All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Vadim Fedorenko <vadfed@meta.com>
Cc: vadim.fedorenko@linux.dev, kuba@kernel.org, martin.lau@linux.dev,
	andrii@kernel.org, ast@kernel.org, mykolal@fb.com,
	herbert@gondor.apana.org.au, netdev@vger.kernel.org,
	linux-crypto@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v10 0/4] BPF crypto API framework
Date: Wed, 24 Apr 2024 23:10:29 +0000	[thread overview]
Message-ID: <171400022908.11196.7603680492975512633.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240422225024.2847039-1-vadfed@meta.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Mon, 22 Apr 2024 15:50:20 -0700 you wrote:
> This series introduces crypto kfuncs to make BPF programs able to
> utilize kernel crypto subsystem. Crypto operations made pluggable to
> avoid extensive growth of kernel when it's not needed. Only skcipher is
> added within this series, but it can be easily extended to other types
> of operations. No hardware offload supported as it needs sleepable
> context which is not available for TX or XDP programs. At the same time
> crypto context initialization kfunc can only run in sleepable context,
> that's why it should be run separately and store the result in the map.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v10,1/4] bpf: make common crypto API for TC/XDP programs
    https://git.kernel.org/bpf/bpf-next/c/3e1c6f35409f
  - [bpf-next,v10,2/4] bpf: crypto: add skcipher to bpf crypto
    https://git.kernel.org/bpf/bpf-next/c/fda4f71282b2
  - [bpf-next,v10,3/4] selftests: bpf: crypto skcipher algo selftests
    https://git.kernel.org/bpf/bpf-next/c/91541ab192fc
  - [bpf-next,v10,4/4] selftests: bpf: crypto: add benchmark for crypto functions
    https://git.kernel.org/bpf/bpf-next/c/8000e627dc98

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



      parent reply	other threads:[~2024-04-24 23:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 22:50 [PATCH bpf-next v10 0/4] BPF crypto API framework Vadim Fedorenko
2024-04-22 22:50 ` [PATCH bpf-next v10 1/4] bpf: make common crypto API for TC/XDP programs Vadim Fedorenko
2024-04-23 11:56   ` kernel test robot
2024-04-24 23:04   ` Martin KaFai Lau
2024-04-22 22:50 ` [PATCH bpf-next v10 2/4] bpf: crypto: add skcipher to bpf crypto Vadim Fedorenko
2024-04-22 22:50 ` [PATCH bpf-next v10 3/4] selftests: bpf: crypto skcipher algo selftests Vadim Fedorenko
2024-04-22 22:50 ` [PATCH bpf-next v10 4/4] selftests: bpf: crypto: add benchmark for crypto functions Vadim Fedorenko
2024-04-24 22:43   ` Martin KaFai Lau
2024-04-24 23:00     ` Vadim Fedorenko
2024-04-24 23:10 ` 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=171400022908.11196.7603680492975512633.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=vadfed@meta.com \
    --cc=vadim.fedorenko@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 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.