oxidecomputer / oxidecomputer/dendrite
LPM V6 table size discrepancy with multicast build
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 4
Description
Once #268 lands. There will be a discrepancy between multicast and non-multicast builds for the V6 LPM table sizes. In particular the IPV6_LPM_SIZE value in constants.p4. When we bring the multicast code out from behind a feature gate, we'll need to address this discrepancy. This conditional compilation was taken as an expedient path to fit #268 in 20 stages with the multicast build.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review #268 and constants.p4, focusing on IPV6_LPM_SIZE and the separate multicast and non-multicast build paths. Determine how the sizes differ when multicast code is brought out from behind the feature gate, while keeping the multicast build within 20 stages. Done means both builds have the intended consistent V6 LPM table sizing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100