> -----Original Message----- > From: Jesper Dangaard Brouer <[email protected]> > Sent: Thursday, April 30, 2020 7:21 AM > To: [email protected] > Cc: Wei Liu <[email protected]>; KY Srinivasan <[email protected]>; > Haiyang Zhang <[email protected]>; Stephen Hemminger > <[email protected]>; Jesper Dangaard Brouer > <[email protected]>; [email protected]; [email protected]; > [email protected]; [email protected]; [email protected]; Toke > Høiland-Jørgensen <[email protected]>; Daniel Borkmann > <[email protected]>; Alexei Starovoitov > <[email protected]>; John Fastabend > <[email protected]>; Alexander Duyck > <[email protected]>; Jeff Kirsher <[email protected]>; > David Ahern <[email protected]>; Willem de Bruijn > <[email protected]>; Ilias Apalodimas > <[email protected]>; Lorenzo Bianconi <[email protected]>; > Saeed Mahameed <[email protected]>; > [email protected] > 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
