[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6609e0a-eb2f-78bd-b565-c56dce9e2e48@gmail.com>
Date: Sun, 27 Sep 2020 20:13:12 -0700
From: David Ahern <dsahern@...il.com>
To: Magnus Karlsson <magnus.karlsson@...il.com>,
Toke Høiland-Jørgensen <toke@...hat.com>
Cc: David Ahern <dahern@...italocean.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
Jason Wang <jasowang@...hat.com>,
David Ahern <dsahern@...nel.org>,
Network Development <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>, kuba@...nel.org,
Jesper Dangaard Brouer <brouer@...hat.com>,
Magnus Karlsson <magnus.karlsson@...el.com>
Subject: Re: [PATCH RFC net-next] virtio_net: Relax queue requirement for
using XDP
On 2/27/20 2:41 AM, Magnus Karlsson wrote:
> I will unfortunately be after Netdevconf due to other commitments. The
> plan is to send out the RFC to the co-authors of the Plumbers
> presentation first, just to check the sanity of it. And after that
> send it to the mailing list. Note that I have taken two shortcuts in
> the RFC to be able to make quicker progress. The first on is the
> driver implementation of the dynamic queue allocation and
> de-allocation. It just does this within a statically pre-allocated set
> of queues. The second is that the user space interface is just a
> setsockopt instead of a rtnetlink interface. Again, just to save some
> time in this initial phase. The information communicated in the
> interface is the same though. In the current code, the queue manager
> can handle the queues of the networking stack, the XDP_TX queues and
> queues allocated by user space and used for AF_XDP. Other uses from
> user space is not covered due to my setsockopt shortcut. Hopefully
> though, this should be enough for an initial assessment.
Any updates on the RFC? I do not recall seeing a patch set on the
mailing list, but maybe I missed it.
Powered by blists - more mailing lists