microsoft / microsoft/demikernel
[inetstack] Support Compile-Time Switch for Prioritizing Wildcard Address Lookup
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 151
- PR merge metrics
- No merged PRs in 30d
Description
Context
When processing incoming packets, we prioritize searching for a socket bound to a specific address rather than searching for a matching socket bound to the wildcard address INADDR_ANY:
The spec does not specify which search should be prioritized over the other, and the current policy may not behave as the majority of other stacks.
Proposed Solution
We should support a compile-time switch that would enable one the choose which searching policy should be prioritized. Furthermore, the default build should be setup to the one matching the behavior of the majority of other stacks.
Contributor guide
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
Start with src/protocols/udp/peer.rs lines 345-356, where the specific-address and wildcard-address lookup priorities are handled. Determine how a compile-time switch can select either policy and establish which behavior should be the default based on other stacks. Done means both policies are selectable and the default matches the majority behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100