> -----Original Message----- > From: Jesper Dangaard Brouer <bro...@redhat.com> > Sent: Thursday, April 30, 2020 7:21 AM > To: same...@amazon.com > Cc: Wei Liu <wei....@kernel.org>; KY Srinivasan <k...@microsoft.com>; > Haiyang Zhang <haiya...@microsoft.com>; Stephen Hemminger > <sthem...@microsoft.com>; Jesper Dangaard Brouer > <bro...@redhat.com>; netdev@vger.kernel.org; b...@vger.kernel.org; > zo...@amazon.com; akiy...@amazon.com; gtza...@amazon.com; Toke > Høiland-Jørgensen <t...@redhat.com>; Daniel Borkmann > <borkm...@iogearbox.net>; Alexei Starovoitov > <alexei.starovoi...@gmail.com>; John Fastabend > <john.fastab...@gmail.com>; Alexander Duyck > <alexander.du...@gmail.com>; Jeff Kirsher <jeffrey.t.kirs...@intel.com>; > David Ahern <dsah...@gmail.com>; Willem de Bruijn > <willemdebruijn.ker...@gmail.com>; Ilias Apalodimas > <ilias.apalodi...@linaro.org>; Lorenzo Bianconi <lore...@kernel.org>; > Saeed Mahameed <sae...@mellanox.com>; > steffen.klass...@secunet.com > Subject: [PATCH net-next v2 12/33] hv_netvsc: add XDP frame size to driver > > The hyperv NIC drivers XDP implementation is rather disappointing as it will > be a slowdown to enable XDP on this driver, given it will allocate a new page > for each packet and copy over the payload, before invoking the XDP BPF- > prog. This needs correction. As I said previously -- This statement is not accurate -- The data path of netvsc driver does memory allocation and copy even without XDP, so it's not "a slowdown to enable XDP".
Thanks, - Haiyang
