public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Vernet <void@manifault.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	martin.lau@linux.dev, kernel-team@fb.com, song@kernel.org,
	yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
	sdf@google.com, haoluo@google.com, jolsa@kernel.org,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org, tj@kernel.org,
	brho@google.com, joshdon@google.com
Subject: Re: [PATCH v6 0/4] bpf: Add user-space-publisher ring buffer map type
Date: Wed, 21 Sep 2022 23:40:16 +0000	[thread overview]
Message-ID: <166380361628.10161.4038336755255982198.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220920000100.477320-1-void@manifault.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Mon, 19 Sep 2022 19:00:56 -0500 you wrote:
> This patch set defines a new map type, BPF_MAP_TYPE_USER_RINGBUF, which
> provides single-user-space-producer / single-kernel-consumer semantics over
> a ring buffer.  Along with the new map type, a helper function called
> bpf_user_ringbuf_drain() is added which allows a BPF program to specify a
> callback with the following signature, to which samples are posted by the
> helper:
> 
> [...]

Here is the summary with links:
  - [v6,1/4] bpf: Define new BPF_MAP_TYPE_USER_RINGBUF map type
    https://git.kernel.org/bpf/bpf-next/c/583c1f420173
  - [v6,2/4] bpf: Add bpf_user_ringbuf_drain() helper
    https://git.kernel.org/bpf/bpf-next/c/205715673844
  - [v6,3/4] bpf: Add libbpf logic for user-space ring buffer
    https://git.kernel.org/bpf/bpf-next/c/b66ccae01f1d
  - [v6,4/4] selftests/bpf: Add selftests validating the user ringbuf
    https://git.kernel.org/bpf/bpf-next/c/e5a9df51c746

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



      parent reply	other threads:[~2022-09-21 23:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20  0:00 [PATCH v6 0/4] bpf: Add user-space-publisher ring buffer map type David Vernet
2022-09-20  0:00 ` [PATCH v6 1/4] bpf: Define new BPF_MAP_TYPE_USER_RINGBUF " David Vernet
2022-09-20  0:00 ` [PATCH v6 2/4] bpf: Add bpf_user_ringbuf_drain() helper David Vernet
2022-09-21 23:33   ` Andrii Nakryiko
2022-09-20  0:00 ` [PATCH v6 3/4] bpf: Add libbpf logic for user-space ring buffer David Vernet
2022-09-20  0:01 ` [PATCH v6 4/4] selftests/bpf: Add selftests validating the user ringbuf David Vernet
2022-09-21 23:40 ` 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=166380361628.10161.4038336755255982198.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=brho@google.com \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=joshdon@google.com \
    --cc=kernel-team@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=tj@kernel.org \
    --cc=void@manifault.com \
    --cc=yhs@fb.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