All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin KaFai Lau <martin.lau@linux.dev>
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,
	maciej.fijalkowski@intel.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v7 0/8] Add kfunc bpf_xdp_pull_data
Date: Tue, 23 Sep 2025 18:41:40 -0700	[thread overview]
Message-ID: <87568a0b-93c8-4fc1-a721-dbfeda01d0bb@linux.dev> (raw)
In-Reply-To: <20250922233356.3356453-1-ameryhung@gmail.com>

On 9/22/25 4:33 PM, Amery Hung wrote:
>    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

Please follow up with a selftest for this change. For global func, there is an 
example in commit 3f23ee5590d9.

>    bpf: Make variables in bpf_prog_test_run_xdp less confusing

This makes the code easier to reason. Thanks. Applied.

>    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


      parent reply	other threads:[~2025-09-24  1:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 23:33 [PATCH bpf-next v7 0/8] Add kfunc bpf_xdp_pull_data Amery Hung
2025-09-22 23:33 ` [PATCH bpf-next v7 1/8] bpf: Clear pfmemalloc flag when freeing all fragments Amery Hung
2025-09-22 23:33 ` [PATCH bpf-next v7 2/8] bpf: Allow bpf_xdp_shrink_data to shrink a frag from head and tail Amery Hung
2025-09-22 23:33 ` [PATCH bpf-next v7 3/8] bpf: Support pulling non-linear xdp data Amery Hung
2025-09-22 23:33 ` [PATCH bpf-next v7 4/8] bpf: Clear packet pointers after changing packet data in kfuncs Amery Hung
2025-09-22 23:33 ` [PATCH bpf-next v7 5/8] bpf: Make variables in bpf_prog_test_run_xdp less confusing Amery Hung
2025-09-22 23:33 ` [PATCH bpf-next v7 6/8] bpf: Support specifying linear xdp packet data size for BPF_PROG_TEST_RUN Amery Hung
2025-09-22 23:33 ` [PATCH bpf-next v7 7/8] selftests/bpf: Test bpf_xdp_pull_data Amery Hung
2025-09-22 23:33 ` [PATCH bpf-next v7 8/8] selftests: drv-net: Pull data before parsing headers Amery Hung
2025-09-24  1:40 ` [PATCH bpf-next v7 0/8] Add kfunc bpf_xdp_pull_data patchwork-bot+netdevbpf
2025-09-24  1:41 ` Martin KaFai Lau [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=87568a0b-93c8-4fc1-a721-dbfeda01d0bb@linux.dev \
    --to=martin.lau@linux.dev \
    --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=maciej.fijalkowski@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.