netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Amery Hung <ameryhung@gmail.com>
Cc: <bpf@vger.kernel.org>, <netdev@vger.kernel.org>,
	<alexei.starovoitov@gmail.com>, <andrii@kernel.org>,
	<daniel@iogearbox.net>, <paul.chaignon@gmail.com>,
	<kuba@kernel.org>, <stfomichev@gmail.com>,
	<martin.lau@kernel.org>, <mohsin.bashr@gmail.com>,
	<noren@nvidia.com>, <dtatulea@nvidia.com>, <saeedm@nvidia.com>,
	<tariqt@nvidia.com>, <mbloch@nvidia.com>, <kernel-team@meta.com>
Subject: Re: [PATCH bpf-next v6 0/7] Add kfunc bpf_xdp_pull_data
Date: Mon, 22 Sep 2025 17:05:09 +0200	[thread overview]
Message-ID: <aNFlpcGxd9yI6qLJ@boxer> (raw)
In-Reply-To: <20250919230952.3628709-1-ameryhung@gmail.com>

On Fri, Sep 19, 2025 at 04:09:45PM -0700, Amery Hung wrote:
> v6 -> v5
>   patch 6
>   - v5 selftest failed on S390 when changing how tailroom occupied by
>     skb_shared_info is calculated. Revert selftest to v4, where we get
>     SKB_DATA_ALIGN(sizeof(struct skb_shared_info)) by running an XDP
>     program

Hi Amery, could you shed more light on this? Would be nice to stick with
BTF approach as it looked clean to me. Was this due to SMP_CACHE_BYTES
being different between archs?

> 
> v5 -> v4
>   patch 1
>   - Add a new patch clearing pfmemalloc bit in xdp->frags when all frags
>     are freed in bpf_xdp_adjust_tail() (Maciej)
> 
>   patch 2
>   - Refactor bpf_xdp_shrink_data() (Maciej)
> 
>   patch 3
>   - Clear pfmemalloc when all frags are freed in bpf_xdp_pull_data()
>     (Maciej)
> 
>   patch 6
>   - Use BTF to get sizes of skb_shared_info and xdp_frame (Maciej)
> 
>   Link: https://lore.kernel.org/bpf/20250919182100.1925352-1-ameryhung@gmail.com/
> 
> v3 -> v4
>   patch 2
>   - Improve comments (Jakub)
>   - Drop new_end and len_free to simplify code (Jakub)
> 
>   patch 4
>   - Instead of adding is_xdp to bpf_test_init, move lower-bound check
>     of user_size to callers (Martin)
>   - Simplify linear data size calculation (Martin)
> 
>   patch 5
>   - Add static function identifier (Martin)
>   - Free calloc-ed buf (Martin)
> 
>   Link: https://lore.kernel.org/bpf/20250917225513.3388199-1-ameryhung@gmail.com/
> 
> v2 -> v3
>   Separate mlx5 fixes from the patchset
> 
>   patch 2
>   - Use headroom for pulling data by shifting metadata and data down
>     (Jakub)
>   - Drop the flags argument (Martin)
> 
>   patch 4 
>   - Support empty linear xdp data for BPF_PROG_TEST_RUN
> 
>   Link: https://lore.kernel.org/bpf/20250915224801.2961360-1-ameryhung@gmail.com/
> 
> v1 -> v2
>   Rebase onto bpf-next
> 
>   Try to build on top of the mlx5 patchset that avoids copying payload
>   to linear part by Christoph but got a kernel panic. Will rebase on
>   that patchset if it got merged first, or separate the mlx5 fix
>   from this set.
> 
>   patch 1
>   - Remove the unnecessary head frag search (Dragos)
>   - Rewind the end frag pointer to simplify the change (Dragos)
>   - Rewind the end frag pointer and recalculate truesize only when the
>     number of frags changed (Dragos)
> 
>   patch 3
>   - Fix len == zero behavior. To mirror bpf_skb_pull_data() correctly,
>     the kfunc should do nothing (Stanislav)
>   - Fix a pointer wrap around bug (Jakub)
>   - Use memmove() when moving sinfo->frags (Jakub)
> 
>   Link: https://lore.kernel.org/bpf/20250905173352.3759457-1-ameryhung@gmail.com/
>   
> ---
> 
> Hi all,
> 
> This patchset introduces a new kfunc bpf_xdp_pull_data() to allow
> pulling nonlinear xdp data. This may be useful when a driver places
> headers in fragments. When an xdp program would like to keep parsing
> packet headers using direct packet access, it can call
> bpf_xdp_pull_data() to make the header available in the linear data
> area. The kfunc can also be used to decapsulate the header in the
> nonlinear data, as currently there is no easy way to do this.
> 
> Tested with the added bpf selftest using bpf test_run and also on
> mlx5 with the tools/testing/selftests/drivers/net/{xdp.py, ping.py}.
> mlx5 with striding RQ enabled always passse xdp_buff with empty linear
> data to xdp programs. xdp.test_xdp_native_pass_mb would fail to parse
> the header before this patchset.
> 
> Thanks!
> Amery
> 
> Amery Hung (7):
>   bpf: Clear pfmemalloc flag when freeing all fragments
>   bpf: Allow bpf_xdp_shrink_data to shrink a frag from head and tail
>   bpf: Support pulling non-linear xdp data
>   bpf: Clear packet pointers after changing packet data in kfuncs
>   bpf: Support specifying linear xdp packet data size for
>     BPF_PROG_TEST_RUN
>   selftests/bpf: Test bpf_xdp_pull_data
>   selftests: drv-net: Pull data before parsing headers
> 
>  include/net/xdp.h                             |   5 +
>  include/net/xdp_sock_drv.h                    |  21 +-
>  kernel/bpf/verifier.c                         |  13 ++
>  net/bpf/test_run.c                            |   9 +-
>  net/core/filter.c                             | 135 +++++++++++--
>  .../bpf/prog_tests/xdp_context_test_run.c     |   4 +-
>  .../selftests/bpf/prog_tests/xdp_pull_data.c  | 179 ++++++++++++++++++
>  .../selftests/bpf/progs/test_xdp_pull_data.c  |  48 +++++
>  .../selftests/net/lib/xdp_native.bpf.c        |  89 +++++++--
>  9 files changed, 463 insertions(+), 40 deletions(-)
>  create mode 100644 tools/testing/selftests/bpf/prog_tests/xdp_pull_data.c
>  create mode 100644 tools/testing/selftests/bpf/progs/test_xdp_pull_data.c
> 
> -- 
> 2.47.3
> 

  parent reply	other threads:[~2025-09-22 15:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 23:09 [PATCH bpf-next v6 0/7] Add kfunc bpf_xdp_pull_data Amery Hung
2025-09-19 23:09 ` [PATCH bpf-next v6 1/7] bpf: Clear pfmemalloc flag when freeing all fragments Amery Hung
2025-09-22 15:05   ` Maciej Fijalkowski
2025-09-19 23:09 ` [PATCH bpf-next v6 2/7] bpf: Allow bpf_xdp_shrink_data to shrink a frag from head and tail Amery Hung
2025-09-22 15:09   ` Maciej Fijalkowski
2025-09-19 23:09 ` [PATCH bpf-next v6 3/7] bpf: Support pulling non-linear xdp data Amery Hung
2025-09-19 23:09 ` [PATCH bpf-next v6 4/7] bpf: Clear packet pointers after changing packet data in kfuncs Amery Hung
2025-09-19 23:09 ` [PATCH bpf-next v6 5/7] bpf: Support specifying linear xdp packet data size for BPF_PROG_TEST_RUN Amery Hung
2025-09-22 19:20   ` Martin KaFai Lau
2025-09-22 19:48     ` Amery Hung
2025-09-22 20:04       ` Martin KaFai Lau
2025-09-22 22:30         ` Amery Hung
2025-09-19 23:09 ` [PATCH bpf-next v6 6/7] selftests/bpf: Test bpf_xdp_pull_data Amery Hung
2025-09-19 23:09 ` [PATCH bpf-next v6 7/7] selftests: drv-net: Pull data before parsing headers Amery Hung
2025-09-22 15:05 ` Maciej Fijalkowski [this message]
2025-09-22 17:46   ` [PATCH bpf-next v6 0/7] Add kfunc bpf_xdp_pull_data Amery Hung

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=aNFlpcGxd9yI6qLJ@boxer \
    --to=maciej.fijalkowski@intel.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ameryhung@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dtatulea@nvidia.com \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=martin.lau@kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=mohsin.bashr@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=noren@nvidia.com \
    --cc=paul.chaignon@gmail.com \
    --cc=saeedm@nvidia.com \
    --cc=stfomichev@gmail.com \
    --cc=tariqt@nvidia.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).