From: Menglong Dong <menglong.dong@linux.dev>
To: Menglong Dong <menglong8.dong@gmail.com>, Jiri Olsa <olsajiri@gmail.com>
Cc: ast@kernel.org, olsajiri@gmail.com, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, shuah@kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2] selftests/bpf: test access to ringbuf position with map pointer
Date: Tue, 24 Mar 2026 17:21:07 +0800 [thread overview]
Message-ID: <2403281.ElGaqSPkdT@7940hx> (raw)
In-Reply-To: <acEdFlYd4UHmknEU@krava>
On 2026/3/23 18:59 Jiri Olsa <olsajiri@gmail.com> write:
> On Mon, Mar 23, 2026 at 10:18:39AM +0800, Menglong Dong wrote:
> > Add the testing to access the bpf_ringbuf with the map pointer.
> > "consumer_pos" and "producer_pos" is accessed in this testing. We reserve
> > 128 bytes in the ringbuf to test the producer_pos, which should be
> > "128 + 8", and the "8" is BPF_RINGBUF_HDR_SZ.
> >
> > It will be helpful if we want to evaluate the usage of the ringbuf in bpf
> > prog with the consumer and producer position.
>
> lgtm, question though.. is this related to some kernel change or
> some ongoing work? looks like basic operation that's already
> tested indirectly by existing tests
I wanted to introduce a kfunc to get the usage of the ringbuf,
then we can wake up the user space lazily if the free space in
the ringbuf is big enough in some case. Then, I found that we
can do it directly with the map ptr. However, I don't see a
test case that read the pointer that come from the map ptr, which
makes me not sure if it is allowed to access the
ringbuf->rb->consumer_pos. So I did the testing, and I worked :)
Thanks!
Menglong Dong
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
>
> jirka
>
> >
> > Signed-off-by: Menglong Dong <dongml2@chinatelecom.cn>
> > Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>
> > ---
> > v2:
> > - don't set the max_entries for the ringbuf map
> > - add comment for the producer_pos
> > ---
> > .../testing/selftests/bpf/progs/map_ptr_kern.c | 18 ++++++++++++++++++
> > 1 file changed, 18 insertions(+)
> >
> > diff --git a/tools/testing/selftests/bpf/progs/map_ptr_kern.c b/tools/testing/selftests/bpf/progs/map_ptr_kern.c
> > index efaf622c28dd..d7611e7018ca 100644
> > --- a/tools/testing/selftests/bpf/progs/map_ptr_kern.c
> > +++ b/tools/testing/selftests/bpf/progs/map_ptr_kern.c
> > @@ -647,8 +647,14 @@ static inline int check_devmap_hash(void)
> > return 1;
> > }
> >
> > +struct bpf_ringbuf {
> > + unsigned long consumer_pos;
> > + unsigned long producer_pos;
> > +} __attribute__((preserve_access_index));
> > +
> > struct bpf_ringbuf_map {
> > struct bpf_map map;
> > + struct bpf_ringbuf *rb;
> > } __attribute__((preserve_access_index));
> >
> > struct {
> > @@ -659,9 +665,21 @@ static inline int check_ringbuf(void)
> > {
> > struct bpf_ringbuf_map *ringbuf = (struct bpf_ringbuf_map *)&m_ringbuf;
> > struct bpf_map *map = (struct bpf_map *)&m_ringbuf;
> > + struct bpf_ringbuf *rb;
> > + void *ptr;
> >
> > VERIFY(check(&ringbuf->map, map, 0, 0, page_size));
> >
> > + ptr = bpf_ringbuf_reserve(&m_ringbuf, 128, 0);
> > + VERIFY(ptr);
> > +
> > + bpf_ringbuf_discard(ptr, 0);
> > + rb = ringbuf->rb;
> > + VERIFY(rb);
> > + VERIFY(rb->consumer_pos == 0);
> > + /* The "8" here is BPF_RINGBUF_HDR_SZ */
> > + VERIFY(rb->producer_pos == 128 + 8);
> > +
> > return 1;
> > }
> >
> > --
> > 2.53.0
> >
>
>
next prev parent reply other threads:[~2026-03-24 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 2:18 [PATCH bpf-next v2] selftests/bpf: test access to ringbuf position with map pointer Menglong Dong
2026-03-23 10:59 ` Jiri Olsa
2026-03-24 9:21 ` Menglong Dong [this message]
2026-03-24 2:53 ` Leon Hwang
2026-03-24 9:24 ` Menglong Dong
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=2403281.ElGaqSPkdT@7940hx \
--to=menglong.dong@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=menglong8.dong@gmail.com \
--cc=olsajiri@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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