From: David Ahern <dsahern@gmail.com>
To: "Magnus Karlsson" <magnus.karlsson@gmail.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: David Ahern <dahern@digitalocean.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
David Ahern <dsahern@kernel.org>,
Network Development <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
kuba@kernel.org, Jesper Dangaard Brouer <brouer@redhat.com>,
Magnus Karlsson <magnus.karlsson@intel.com>
Subject: Re: [PATCH RFC net-next] virtio_net: Relax queue requirement for using XDP
Date: Sun, 27 Sep 2020 20:13:12 -0700 [thread overview]
Message-ID: <b6609e0a-eb2f-78bd-b565-c56dce9e2e48@gmail.com> (raw)
In-Reply-To: <CAJ8uoz2++_D_XFwUjFri0HmNaNWKtiPNrJr=Fvc8grj-8hRzfg@mail.gmail.com>
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.
next prev parent reply other threads:[~2020-09-28 3:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 0:57 [PATCH RFC net-next] virtio_net: Relax queue requirement for using XDP David Ahern
2020-02-26 1:37 ` Jakub Kicinski
2020-02-26 3:00 ` Jason Wang
2020-02-26 3:24 ` David Ahern
2020-02-26 3:29 ` Jason Wang
2020-02-26 3:34 ` David Ahern
2020-02-26 3:52 ` Jason Wang
2020-02-26 4:35 ` David Ahern
2020-02-26 5:51 ` Jason Wang
2020-02-26 8:19 ` Toke Høiland-Jørgensen
2020-02-26 8:23 ` Michael S. Tsirkin
2020-02-26 8:34 ` Toke Høiland-Jørgensen
2020-02-26 8:42 ` Michael S. Tsirkin
2020-02-26 9:02 ` Toke Høiland-Jørgensen
2020-02-26 9:32 ` Michael S. Tsirkin
2020-02-26 15:58 ` David Ahern
2020-02-26 16:21 ` Toke Høiland-Jørgensen
2020-02-26 17:08 ` Michael S. Tsirkin
2020-02-26 21:31 ` Toke Høiland-Jørgensen
2020-02-27 3:27 ` David Ahern
2020-02-27 10:19 ` Toke Høiland-Jørgensen
2020-02-27 10:41 ` Magnus Karlsson
2020-09-28 3:13 ` David Ahern [this message]
2020-09-28 14:25 ` Magnus Karlsson
2020-09-29 2:44 ` David Ahern
2020-02-26 6:48 ` Michael S. Tsirkin
2020-02-26 7:28 ` Jason Wang
2020-02-26 8:21 ` Michael S. Tsirkin
2020-02-26 6:43 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b6609e0a-eb2f-78bd-b565-c56dce9e2e48@gmail.com \
--to=dsahern@gmail.com \
--cc=brouer@redhat.com \
--cc=dahern@digitalocean.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=jasowang@redhat.com \
--cc=kuba@kernel.org \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).