xdp-for-windows
xdp-for-windows copied to clipboard
XDP speeds up networking on Windows
The logs that are collected from test failures should include at least a minimal number of events from the test code, such as test failures. I _think_ the easiest way...
For NetVSC, interfaces will need to dynamically close queues. Add an XDP callback to initiate queue teardown. Partially implemented: see XdpTxQueueNotify.
How do we support Linux apps? Lowest common denominator of Windows/Linux features? If Windows XDP adds a new feature, can we avoid divergence if Linux adds a similar feature later?
A partner requested the ability to loop back TX onto an RX queue.
Expose perf/diagnostics counters. Query using XDP APIs and/or expose through Windows perf counter framework?
A scalable (good performance w/ lots idle sockets) poke+wait multi socket API may be useful. Should be based on the ProcessSocketNotifications API and similarly support IOCPs. This may also support...
This race condition applies to all offloads. XdpGenericRssInitialize: // // Attempt to query the indirection table. // // TODO: how do we avoid a race with the protocol driver plumbing...
Found in https://dev.azure.com/mscodehub/WindowsXDP/_git/xdp/pullrequest/19220 Add support for querying NdisGetRssProcessorInformation from LWFs XdpGenericRssInitialize: // // RSS allows more processors than receive queues, but the RSS // implementation in TCPIP constrains the number...
When XDP transitions from independently managing RSS for each edge to letting upper layer components manage the miniport RSS (RemoveLowerEdgeRssSetting), XDP must perform 2 actions: 1) Plumb the upper edge...