public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	steffen.klassert@secunet.com, antony.antony@secunet.com,
	alexei.starovoitov@gmail.com, yonghong.song@linux.dev,
	eddyz87@gmail.com, eyal.birger@gmail.com, devel@linux-ipsec.org
Subject: Re: [PATCH bpf-next v6 0/5] Add bpf_xdp_get_xfrm_state() kfunc
Date: Fri, 15 Dec 2023 01:30:25 +0000	[thread overview]
Message-ID: <170260382549.15017.6886623501178455100.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1702593901.git.dxu@dxuuu.xyz>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu, 14 Dec 2023 15:49:01 -0700 you wrote:
> This patchset adds two kfunc helpers, bpf_xdp_get_xfrm_state() and
> bpf_xdp_xfrm_state_release() that wrap xfrm_state_lookup() and
> xfrm_state_put(). The intent is to support software RSS (via XDP) for
> the ongoing/upcoming ipsec pcpu work [0]. Recent experiments performed
> on (hopefully) reproducible AWS testbeds indicate that single tunnel
> pcpu ipsec can reach line rate on 100G ENA nics.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v6,1/5] bpf: xfrm: Add bpf_xdp_get_xfrm_state() kfunc
    https://git.kernel.org/bpf/bpf-next/c/8f0ec8c68175
  - [bpf-next,v6,2/5] bpf: selftests: test_tunnel: Setup fresh topology for each subtest
    https://git.kernel.org/bpf/bpf-next/c/77a7a8220f0d
  - [bpf-next,v6,3/5] bpf: selftests: test_tunnel: Use vmlinux.h declarations
    https://git.kernel.org/bpf/bpf-next/c/02b4e126e6a5
  - [bpf-next,v6,4/5] bpf: selftests: Move xfrm tunnel test to test_progs
    https://git.kernel.org/bpf/bpf-next/c/e7adc8291a9e
  - [bpf-next,v6,5/5] bpf: xfrm: Add selftest for bpf_xdp_get_xfrm_state()
    https://git.kernel.org/bpf/bpf-next/c/2cd07b0eb08c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-12-15  1:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 22:49 [PATCH bpf-next v6 0/5] Add bpf_xdp_get_xfrm_state() kfunc Daniel Xu
2023-12-14 22:49 ` [PATCH bpf-next v6 1/5] bpf: xfrm: " Daniel Xu
2023-12-14 22:49 ` [PATCH bpf-next v6 2/5] bpf: selftests: test_tunnel: Setup fresh topology for each subtest Daniel Xu
2023-12-14 22:49 ` [PATCH bpf-next v6 3/5] bpf: selftests: test_tunnel: Use vmlinux.h declarations Daniel Xu
2023-12-14 22:49 ` [PATCH bpf-next v6 4/5] bpf: selftests: Move xfrm tunnel test to test_progs Daniel Xu
2023-12-14 22:49 ` [PATCH bpf-next v6 5/5] bpf: xfrm: Add selftest for bpf_xdp_get_xfrm_state() Daniel Xu
2023-12-15  1:30 ` patchwork-bot+netdevbpf [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=170260382549.15017.6886623501178455100.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=antony.antony@secunet.com \
    --cc=bpf@vger.kernel.org \
    --cc=devel@linux-ipsec.org \
    --cc=dxu@dxuuu.xyz \
    --cc=eddyz87@gmail.com \
    --cc=eyal.birger@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=yonghong.song@linux.dev \
    /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