Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NOT WORKING] Compile with larger tables #6

Closed
wants to merge 19 commits into from
Closed

Conversation

ccascone
Copy link
Member

@ccascone ccascone commented Jun 11, 2020

The sizing is the same used for fabric-tofino.

Build works, but for some reason when running PTF tests stratum-bfrt fails with the following error (from ptf/run/tm/log/stratum-bf/stratum_bf.log):

2020-06-11 19:47:04.799027 BF_BFRT FATAL - Unable to find any BfRt Json File
2020-06-11 19:47:04.800393 BF_BFRT ERROR - makeBfRtInfo:461 Failed to create BfRtInfo for dev_id  0

Yi Tseng and others added 19 commits May 23, 2020 21:03
Licenses
Makefile from fabric-tofino
Move P4 code to src/main/p4
Add PipeconfLoader and pom file
Add bridge metadata and use different metadata for ingress and egress
metadata.
Supports basic fabric functionality:
 - packetio
 - IPv4 unicast
 - MPLS
 - L2 bridging

Work in progress:
 - multicast
 - double vlan tagging
 - IPv6 unicast
 - remove unused comment
 - fabric -> fabric-tna
The new Stratum fixed the CPU port issue
 - add new device "stratum-bfrt" to PTF
 - restructure repo
   - move p4 source code to /p4src
   - new script to build pipeline tar
 - add new pipeconf for stratum_bfrt
   - Needs "RAW_DEVICE_CONFIG" extension support
- update PTF test script
- custom flags for stratum-bfrt docker container
- Use stratum-bfrt as the default stratum binary
Added instructions on how to obtain and load the stratum-bfrt docker image. Also, I moved instructions for setting `STRATUM_BF_DOCKER_FLAG` as an optional last step, as that was preventing the stratum container to start (it was looking to mount `abs-path-to-stratum_bfrt` which didn't exist on my machine).

Apart from this, instructions work well. I was able to run all tests (excluding multicast and packet I/0 for which we don't have support yet).
bfrt_python CLI will use pipeline name as a variable name in shell.
We cannot use a name with "-" as a variable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants