From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexander Lobakin <aleksander.lobakin@intel.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] Change BPF_TEST_RUN use the system page pool for live XDP frames
Date: Mon, 19 Feb 2024 19:52:05 +0100 [thread overview]
Message-ID: <87wmr0b82y.fsf@toke.dk> (raw)
In-Reply-To: <20240215132634.474055-1-toke@redhat.com>
Toke Høiland-Jørgensen <toke@redhat.com> writes:
> Now that we have a system-wide page pool, we can use that for the live
> frame mode of BPF_TEST_RUN (used by the XDP traffic generator), and
> avoid the cost of creating a separate page pool instance for each
> syscall invocation. See the individual patches for more details.
>
> Toke Høiland-Jørgensen (3):
> net: Register system page pool as an XDP memory model
> bpf: test_run: Use system page pool for XDP live frame mode
> bpf: test_run: Fix cacheline alignment of live XDP frame data
> structures
>
> include/linux/netdevice.h | 1 +
> net/bpf/test_run.c | 138 +++++++++++++++++++-------------------
> net/core/dev.c | 13 +++-
> 3 files changed, 81 insertions(+), 71 deletions(-)
Hi maintainers
This series is targeting net-next, but it's listed as delegate:bpf in
patchwork[0]; is that a mistake? Do I need to do anything more to nudge it
along?
-Toke
[0] https://patchwork.kernel.org/project/netdevbpf/list/?series=826384
next prev parent reply other threads:[~2024-02-19 18:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 13:26 [PATCH net-next 0/3] Change BPF_TEST_RUN use the system page pool for live XDP frames Toke Høiland-Jørgensen
2024-02-15 13:26 ` [PATCH net-next 1/3] net: Register system page pool as an XDP memory model Toke Høiland-Jørgensen
2024-02-15 13:26 ` [PATCH net-next 2/3] bpf: test_run: Use system page pool for XDP live frame mode Toke Høiland-Jørgensen
2024-02-20 9:06 ` Daniel Borkmann
2024-02-20 9:45 ` Paolo Abeni
2024-02-20 13:14 ` Toke Høiland-Jørgensen
2024-02-20 14:57 ` Paolo Abeni
2024-02-20 19:33 ` Toke Høiland-Jørgensen
2024-02-15 13:26 ` [PATCH net-next 3/3] bpf: test_run: Fix cacheline alignment of live XDP frame data structures Toke Høiland-Jørgensen
2024-02-20 9:06 ` Daniel Borkmann
2024-02-15 15:30 ` [PATCH net-next 0/3] Change BPF_TEST_RUN use the system page pool for live XDP frames Alexander Lobakin
2024-02-15 17:06 ` Toke Høiland-Jørgensen
2024-02-16 11:41 ` Alexander Lobakin
2024-02-16 14:00 ` Toke Høiland-Jørgensen
2024-02-19 18:52 ` Toke Høiland-Jørgensen [this message]
2024-02-20 8:39 ` Daniel Borkmann
2024-02-20 9:03 ` Paolo Abeni
2024-02-20 9:19 ` Daniel Borkmann
2024-02-20 11:23 ` Toke Høiland-Jørgensen
2024-02-20 12:35 ` Daniel Borkmann
2024-02-20 15:24 ` Toke Høiland-Jørgensen
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=87wmr0b82y.fsf@toke.dk \
--to=toke@redhat.com \
--cc=aleksander.lobakin@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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).