aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/networking/device_drivers/microsoft
diff options
context:
space:
mode:
authorHaiyang Zhang <haiyangz@microsoft.com>2020-01-23 13:52:34 -0800
committerDavid S. Miller <davem@davemloft.net>2020-01-25 10:43:19 +0100
commit351e1581395fcc7fb952bbd7dda01238f69968fd (patch)
tree603affba2df25970a5036668b79c1717212e7dba /Documentation/networking/device_drivers/microsoft
parentdevlink: Add health recover notifications on devlink flows (diff)
downloadlinux-dev-351e1581395fcc7fb952bbd7dda01238f69968fd.tar.xz
linux-dev-351e1581395fcc7fb952bbd7dda01238f69968fd.zip
hv_netvsc: Add XDP support
This patch adds support of XDP in native mode for hv_netvsc driver, and transparently sets the XDP program on the associated VF NIC as well. Setting / unsetting XDP program on synthetic NIC (netvsc) propagates to VF NIC automatically. Setting / unsetting XDP program on VF NIC directly is not recommended, also not propagated to synthetic NIC, and may be overwritten by setting of synthetic NIC. The Azure/Hyper-V synthetic NIC receive buffer doesn't provide headroom for XDP. We thought about re-use the RNDIS header space, but it's too small. So we decided to copy the packets to a page buffer for XDP. And, most of our VMs on Azure have Accelerated Network (SRIOV) enabled, so most of the packets run on VF NIC. The synthetic NIC is considered as a fallback data-path. So the data copy on netvsc won't impact performance significantly. XDP program cannot run with LRO (RSC) enabled, so you need to disable LRO before running XDP: ethtool -K eth0 lro off XDP actions not yet supported: XDP_REDIRECT Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/networking/device_drivers/microsoft')
0 files changed, 0 insertions, 0 deletions