microsoft / microsoft/demikernel
[inetstack] Retry on failed transmit for ARP and ICMP
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 151
- PR merge metrics
- No merged PRs in 30d
Description
Context
Currently, when we fail to send a response to either an ARP request or a ping, we simply wait for the other end to retry. It would be better to retry the send ourselves instead of treating it like a dropped packet.
Proposed Solution
Implement a simple retry mechanism for transmit on response to ARP or ping requests.
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 by locating the inetstack paths that transmit responses to ARP requests and ping requests, then inspect how failed sends are handled. Define the retry behavior for both response types and verify that failed transmissions are retried rather than treated as dropped packets.
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