* [PATCH bpf-next] selftests/bpf: test access to ringbuf position with map pointer
@ 2026-03-20 8:41 Menglong Dong
2026-03-20 12:40 ` Jiri Olsa
2026-03-22 1:51 ` Emil Tsalapatis
0 siblings, 2 replies; 5+ messages in thread
From: Menglong Dong @ 2026-03-20 8:41 UTC (permalink / raw)
To: ast
Cc: daniel, andrii, martin.lau, eddyz87, song, yonghong.song,
john.fastabend, kpsingh, sdf, haoluo, jolsa, shuah, bpf,
linux-kselftest, linux-kernel
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.
Signed-off-by: Menglong Dong <dongml2@chinatelecom.cn>
---
.../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..c3fa57ec430b 100644
--- a/tools/testing/selftests/bpf/progs/map_ptr_kern.c
+++ b/tools/testing/selftests/bpf/progs/map_ptr_kern.c
@@ -647,21 +647,39 @@ 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 {
__uint(type, BPF_MAP_TYPE_RINGBUF);
+ __uint(max_entries, 1 << 10);
} m_ringbuf SEC(".maps");
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);
+ VERIFY(rb->producer_pos == 128 + 8);
+
return 1;
}
--
2.53.0
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH bpf-next] selftests/bpf: test access to ringbuf position with map pointer
2026-03-20 8:41 [PATCH bpf-next] selftests/bpf: test access to ringbuf position with map pointer Menglong Dong
@ 2026-03-20 12:40 ` Jiri Olsa
2026-03-21 7:37 ` Menglong Dong
2026-03-22 1:51 ` Emil Tsalapatis
1 sibling, 1 reply; 5+ messages in thread
From: Jiri Olsa @ 2026-03-20 12:40 UTC (permalink / raw)
To: Menglong Dong
Cc: ast, daniel, andrii, martin.lau, eddyz87, song, yonghong.song,
john.fastabend, kpsingh, sdf, haoluo, shuah, bpf, linux-kselftest,
linux-kernel
On Fri, Mar 20, 2026 at 04:41:55PM +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.
>
> Signed-off-by: Menglong Dong <dongml2@chinatelecom.cn>
> ---
> .../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..c3fa57ec430b 100644
> --- a/tools/testing/selftests/bpf/progs/map_ptr_kern.c
> +++ b/tools/testing/selftests/bpf/progs/map_ptr_kern.c
> @@ -647,21 +647,39 @@ 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 {
> __uint(type, BPF_MAP_TYPE_RINGBUF);
> + __uint(max_entries, 1 << 10);
do you need to set max_entries? there's already check below
making sure it's 4096
jirka
> } m_ringbuf SEC(".maps");
>
> 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);
> + VERIFY(rb->producer_pos == 128 + 8);
> +
> return 1;
> }
>
> --
> 2.53.0
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH bpf-next] selftests/bpf: test access to ringbuf position with map pointer
2026-03-20 12:40 ` Jiri Olsa
@ 2026-03-21 7:37 ` Menglong Dong
0 siblings, 0 replies; 5+ messages in thread
From: Menglong Dong @ 2026-03-21 7:37 UTC (permalink / raw)
To: Menglong Dong, Jiri Olsa
Cc: ast, daniel, andrii, martin.lau, eddyz87, song, yonghong.song,
john.fastabend, kpsingh, sdf, haoluo, shuah, bpf, linux-kselftest,
linux-kernel
On 2026/3/20 20:40, Jiri Olsa wrote:
> On Fri, Mar 20, 2026 at 04:41:55PM +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.
> >
> > Signed-off-by: Menglong Dong <dongml2@chinatelecom.cn>
> > ---
> > .../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..c3fa57ec430b 100644
> > --- a/tools/testing/selftests/bpf/progs/map_ptr_kern.c
> > +++ b/tools/testing/selftests/bpf/progs/map_ptr_kern.c
> > @@ -647,21 +647,39 @@ 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 {
> > __uint(type, BPF_MAP_TYPE_RINGBUF);
> > + __uint(max_entries, 1 << 10);
>
> do you need to set max_entries? there's already check below
> making sure it's 4096
Hi, Jiri. Thanks for the reviewing. You are right, we don't
need to set the max_entries here, as it will be set in the
test_map_ptr(). I'll remove this part in V2.
Thanks!
Menglong Dong
>
> jirka
>
>
> > } m_ringbuf SEC(".maps");
> >
> > 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);
> > + VERIFY(rb->producer_pos == 128 + 8);
> > +
> > return 1;
> > }
> >
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH bpf-next] selftests/bpf: test access to ringbuf position with map pointer
2026-03-20 8:41 [PATCH bpf-next] selftests/bpf: test access to ringbuf position with map pointer Menglong Dong
2026-03-20 12:40 ` Jiri Olsa
@ 2026-03-22 1:51 ` Emil Tsalapatis
2026-03-23 2:06 ` Menglong Dong
1 sibling, 1 reply; 5+ messages in thread
From: Emil Tsalapatis @ 2026-03-22 1:51 UTC (permalink / raw)
To: Menglong Dong, ast
Cc: daniel, andrii, martin.lau, eddyz87, song, yonghong.song,
john.fastabend, kpsingh, sdf, haoluo, jolsa, shuah, bpf,
linux-kselftest, linux-kernel
On Fri Mar 20, 2026 at 4:41 AM EDT, 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.
>
> Signed-off-by: Menglong Dong <dongml2@chinatelecom.cn>
Once Jiri's feedback is addressed feel free to add:
Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>
One nit below.
> ---
> .../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..c3fa57ec430b 100644
> --- a/tools/testing/selftests/bpf/progs/map_ptr_kern.c
> +++ b/tools/testing/selftests/bpf/progs/map_ptr_kern.c
> @@ -647,21 +647,39 @@ 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 {
> __uint(type, BPF_MAP_TYPE_RINGBUF);
> + __uint(max_entries, 1 << 10);
> } m_ringbuf SEC(".maps");
>
> 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);
Nit: Can you repeat here the explanation from the cover letter
as to why this is 128 + 8?
> + VERIFY(rb->producer_pos == 128 + 8);
> +
> return 1;
> }
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH bpf-next] selftests/bpf: test access to ringbuf position with map pointer
2026-03-22 1:51 ` Emil Tsalapatis
@ 2026-03-23 2:06 ` Menglong Dong
0 siblings, 0 replies; 5+ messages in thread
From: Menglong Dong @ 2026-03-23 2:06 UTC (permalink / raw)
To: Menglong Dong, ast, Emil Tsalapatis
Cc: daniel, andrii, martin.lau, eddyz87, song, yonghong.song,
john.fastabend, kpsingh, sdf, haoluo, jolsa, shuah, bpf,
linux-kselftest, linux-kernel
On 2026/3/22 09:51 Emil Tsalapatis <emil@etsalapatis.com> write:
> On Fri Mar 20, 2026 at 4:41 AM EDT, 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.
> >
> > Signed-off-by: Menglong Dong <dongml2@chinatelecom.cn>
>
> Once Jiri's feedback is addressed feel free to add:
>
> Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>
>
> One nit below.
[...]
> > + VERIFY(rb->consumer_pos == 0);
>
> Nit: Can you repeat here the explanation from the cover letter
> as to why this is 128 + 8?
OK, I'll add a comment here.
Thanks!
Menglong Dong
>
> > + VERIFY(rb->producer_pos == 128 + 8);
> > +
> > return 1;
> > }
>
> >
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-03-23 2:06 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-03-20 8:41 [PATCH bpf-next] selftests/bpf: test access to ringbuf position with map pointer Menglong Dong
2026-03-20 12:40 ` Jiri Olsa
2026-03-21 7:37 ` Menglong Dong
2026-03-22 1:51 ` Emil Tsalapatis
2026-03-23 2:06 ` Menglong Dong
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox