feature request: set appropriate qdisc on Azure Accelerated Networking interfaces
- Dominant language
- Python
- Stars
- 11
- Forks
- 24
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 1
Description
When SR-IOV network devices are used with Azure Accelerated Networking, a VM sees two interfaces configured in a bonded pair. Details are at https://learn.microsoft.com/en-us/azure/virtual-network/accelerated-networking-how-it-works By default, Linux distributions will attach the default TX queueing discipline to both interfaces, which is redundant and has observed to lead to performance degredation. An optimal configuration would configure a qdisc on the physical VF and `noqueue` on the synthetic interface.
See https://github.com/flatcar/Flatcar/issues/1458 for context, and note that the exact solution is still being discussed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Azure Accelerated Networking documentation linked in the issue and the Flatcar issue #1458 for context on the bonded SR-IOV interfaces. The exact solution is still under discussion; this is done only once an agreed configuration sets an appropriate qdisc on the physical VF and noqueue on the synthetic interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, linux, python
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100