[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bcfd90dd-4977-4f97-daec-c7128bcdb67e@fb.com>
Date: Wed, 11 Apr 2018 11:43:35 -0700
From: Alexei Starovoitov <ast@...com>
To: Björn Töpel <bjorn.topel@...il.com>,
William Tu <u9012063@...il.com>
CC: "Karlsson, Magnus" <magnus.karlsson@...el.com>,
Alexander Duyck <alexander.h.duyck@...el.com>,
Alexander Duyck <alexander.duyck@...il.com>,
John Fastabend <john.fastabend@...il.com>,
Jesper Dangaard Brouer <brouer@...hat.com>,
Willem de Bruijn <willemdebruijn.kernel@...il.com>,
Daniel Borkmann <daniel@...earbox.net>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
Björn Töpel <bjorn.topel@...el.com>,
<michael.lundkvist@...csson.com>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
Anjali Singhai Jain <anjali.singhai@...el.com>,
"Zhang, Qi Z" <qi.z.zhang@...el.com>, <ravineet.singh@...csson.com>
Subject: Re: [RFC PATCH v2 00/14] Introducing AF_XDP support
On 4/11/18 5:17 AM, Björn Töpel wrote:
>
> In the current RFC you are required to create both an Rx and Tx queue
> to bind the socket, which is just weird for your "Rx on one device, Tx
> to another" scenario. I'll fix that in the next RFC.
I would defer on adding new features until the key functionality lands.
imo it's in good shape and I would submit it without RFC tag as soon as
net-next reopens.
Powered by blists - more mailing lists