From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/4] Change BPF_TEST_RUN use the system page pool for live XDP frames
Date: Wed, 21 Feb 2024 15:45:19 +0100 [thread overview]
Message-ID: <87v86hzxj4.fsf@toke.dk> (raw)
In-Reply-To: <20240220210342.40267-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.
>
> This series targets net-next because it depends on this series of
> Lorenzo's, that adds a global system page pool:
>
> https://lore.kernel.org/r/cover.1707729884.git.lorenzo@kernel.org
>
> Changelog:
> v2:
> - Change the cookie that marks the page for recycling to be a 128-bit
> value (Paolo)
Alright> - Add a patch that removes the init_callback parameter from page
> pool (Olek)
> - Carry forward review tags from v1
>
> Toke Høiland-Jørgensen (4):
> 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
> page pool: Remove init_callback parameter
>
> include/linux/netdevice.h | 1 +
> include/net/page_pool/types.h | 4 -
> net/bpf/test_run.c | 143 +++++++++++++++++-----------------
> net/core/dev.c | 13 +++-
> net/core/page_pool.c | 4 -
> 5 files changed, 86 insertions(+), 79 deletions(-)
>
> --
> 2.43.0
prev parent reply other threads:[~2024-02-21 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 21:03 [PATCH net-next v2 0/4] Change BPF_TEST_RUN use the system page pool for live XDP frames Toke Høiland-Jørgensen
2024-02-21 14:45 ` Toke Høiland-Jørgensen [this message]
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=87v86hzxj4.fsf@toke.dk \
--to=toke@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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