From: David Vernet <void@manifault.com>
To: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
daniel@iogearbox.net
Cc: haoluo@google.com, joannelkoong@gmail.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
sdf@google.com, song@kernel.org, yhs@fb.com, kernel-team@fb.com,
tj@kernel.org
Subject: Re: [PATCH v2 0/4] bpf: Add user-space-publisher ringbuffer map type
Date: Thu, 11 Aug 2022 18:59:48 -0500 [thread overview]
Message-ID: <YvWX9GrJuTYfjjlK@maniforge.dhcp.thefacebook.com> (raw)
In-Reply-To: <20220811234941.887747-1-void@manifault.com>
On Thu, Aug 11, 2022 at 06:49:37PM -0500, David Vernet 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 ringbuffer. 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:
[...]
I just noticed that Andrii left some comments on v1 about 20 mins ago.
Please disregard this version -- I'll apply Andrii's comments and then send
out a follow on v3 version.
prev parent reply other threads:[~2022-08-11 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 23:49 David Vernet
2022-08-11 23:49 ` [PATCH v2 1/4] bpf: Define new BPF_MAP_TYPE_USER_RINGBUF " David Vernet
2022-08-11 23:49 ` [PATCH v2 2/4] bpf: Add bpf_user_ringbuf_drain() helper David Vernet
2022-08-15 21:23 ` Hao Luo
2022-08-16 13:20 ` David Vernet
2022-08-16 18:24 ` Hao Luo
2022-08-11 23:49 ` [PATCH v2 3/4] bpf: Add libbpf logic for user-space ring buffer David Vernet
2022-08-11 23:49 ` [PATCH v2 4/4] selftests/bpf: Add selftests validating the user ringbuf David Vernet
2022-08-11 23:59 ` David Vernet [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=YvWX9GrJuTYfjjlK@maniforge.dhcp.thefacebook.com \
--to=void@manifault.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=joannelkoong@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--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=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
all inboxes | Powered by JetHome®