[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190623162133.6b7f24e1@carbon>
Date: Sun, 23 Jun 2019 16:21:33 +0200
From: Jesper Dangaard Brouer <brouer@...hat.com>
To: <sameehj@...zon.com>
Cc: brouer@...hat.com, <davem@...emloft.net>, <netdev@...r.kernel.org>,
<dwmw@...zon.com>, "Machulsky, Zorik" <zorik@...zon.com>,
<matua@...zon.com>, <saeedb@...zon.com>, <msw@...zon.com>,
<aliguori@...zon.com>, <nafea@...zon.com>, <gtzalik@...zon.com>,
<netanel@...zon.com>, <alisaidi@...zon.com>, <benh@...zon.com>,
<akiyano@...zon.com>, Daniel Borkmann <borkmann@...earbox.net>
Subject: Re: [RFC V1 net-next 1/1] net: ena: implement XDP drop support
On Sun, 23 Jun 2019 10:06:49 +0300 <sameehj@...zon.com> wrote:
> This commit implements the basic functionality of drop/pass logic in the
> ena driver.
Usually we require a driver to implement all the XDP return codes,
before we accept it. But as Daniel and I discussed with Zorik during
NetConf[1], we are going to make an exception and accept the driver
if you also implement XDP_TX.
As we trust that Zorik/Amazon will follow and implement XDP_REDIRECT
later, given he/you wants AF_XDP support which requires XDP_REDIRECT.
[1] http://vger.kernel.org/netconf2019.html
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
Powered by blists - more mailing lists