From: Zvi Effron <zeffron@riotgames.com>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: Xu Kuohai <xukuohai@huaweicloud.com>,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Yonghong Song <yhs@fb.com>, Song Liu <song@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
Shuah Khan <shuah@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Willem de Bruijn <willemb@google.com>,
Jason Xing <kerneljasonxing@gmail.com>,
Paul Chaignon <paul.chaignon@gmail.com>,
Tao Chen <chen.dylane@linux.dev>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Martin Kelly <martin.kelly@crowdstrike.com>
Subject: Re: [PATCH bpf-next 2/4] libbpf: ringbuf: Add overwrite ring buffer process
Date: Thu, 14 Aug 2025 14:20:20 -0700 [thread overview]
Message-ID: <CAC1LvL1=61DYMAG=c57LRns++9rHF_thD3Kn=nopUoi8CkPshA@mail.gmail.com> (raw)
In-Reply-To: <8d9cdce252162519c7679132a5e3235d03ac97c0.camel@gmail.com>
On Thu, Aug 14, 2025 at 12:34 PM Eduard Zingerman <eddyz87@gmail.com> wrote:
>
> On Mon, 2025-08-04 at 10:20 +0800, Xu Kuohai wrote:
>
> [...]
>
> > @@ -278,6 +293,92 @@ static int64_t ringbuf_process_ring(struct ring *r, size_t n)
> > return cnt;
> > }
> >
> > +static int64_t ringbuf_process_overwrite_ring(struct ring *r, size_t n)
> > +{
> > +
> > + int err;
> > + uint32_t *len_ptr, len;
> > + /* 64-bit to avoid overflow in case of extreme application behavior */
> > + int64_t cnt = 0;
> > + size_t size, offset;
> > + unsigned long cons_pos, prod_pos, over_pos, tmp_pos;
> > + bool got_new_data;
> > + void *sample;
> > + bool copied;
> > +
> > + size = r->mask + 1;
> > +
> > + cons_pos = smp_load_acquire(r->consumer_pos);
> > + do {
> > + got_new_data = false;
> > +
> > + /* grab a copy of data */
> > + prod_pos = smp_load_acquire(r->producer_pos);
> > + do {
> > + over_pos = READ_ONCE(*r->overwrite_pos);
> > + /* prod_pos may be outdated now */
> > + if (over_pos < prod_pos) {
> > + tmp_pos = max(cons_pos, over_pos);
> > + /* smp_load_acquire(r->producer_pos) before
> > + * READ_ONCE(*r->overwrite_pos) ensures that
> > + * over_pos + r->mask < prod_pos never occurs,
> > + * so size is never larger than r->mask
> > + */
> > + size = prod_pos - tmp_pos;
> > + if (!size)
> > + goto done;
> > + memcpy(r->read_buffer,
> > + r->data + (tmp_pos & r->mask), size);
> > + copied = true;
> > + } else {
> > + copied = false;
> > + }
> > + prod_pos = smp_load_acquire(r->producer_pos);
> > + /* retry if data is overwritten by producer */
> > + } while (!copied || prod_pos - tmp_pos > r->mask);
>
> Could you please elaborate a bit, why this condition is sufficient to
> guarantee that r->overwrite_pos had not changed while memcpy() was
> executing?
>
It isn't sufficient to guarantee that, but does it need tobe ? The concern is
that the data being memcpy-ed might have been overwritten, right? This
condition is sufficient to guarantee that can't happen without forcing another
loop iteration.
For the producer to overwrite a memcpy-ed byte, it must have looped around the
entire buffer, so r->producer_pos will be at least r->mask + 1 more than
tmp_pos. The +1 is because r->producer_pos first had to produce the byte
that got overwritten for it to be included in the memcpy, then produce it a
second time to overwrite it.
Since the code rereads r->producer_pos before making the check, if any bytes
have been overwritten, prod_pos - tmp_pos will be at least r->mask + 1, so the
check will return true and the loop will iterate again, and a new memcpy will
be performed.
> > +
> > + cons_pos = tmp_pos;
> > +
> > + for (offset = 0; offset < size; offset += roundup_len(len)) {
> > + len_ptr = r->read_buffer + (offset & r->mask);
> > + len = *len_ptr;
> > +
> > + if (len & BPF_RINGBUF_BUSY_BIT)
> > + goto done;
> > +
> > + got_new_data = true;
> > + cons_pos += roundup_len(len);
> > +
> > + if ((len & BPF_RINGBUF_DISCARD_BIT) == 0) {
> > + sample = (void *)len_ptr + BPF_RINGBUF_HDR_SZ;
> > + err = r->sample_cb(r->ctx, sample, len);
> > + if (err < 0) {
> > + /* update consumer pos and bail out */
> > + smp_store_release(r->consumer_pos,
> > + cons_pos);
> > + return err;
> > + }
> > + cnt++;
> > + }
> > +
> > + if (cnt >= n)
> > + goto done;
> > + }
> > + } while (got_new_data);
> > +
> > +done:
> > + smp_store_release(r->consumer_pos, cons_pos);
> > + return cnt;
> > +}
>
> [...]
>
next prev parent reply other threads:[~2025-08-14 21:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 2:20 [PATCH bpf-next 0/4] Add overwrite mode for bpf ring buffer Xu Kuohai
2025-08-04 2:20 ` [PATCH bpf-next 1/4] bpf: " Xu Kuohai
2025-08-08 21:39 ` Alexei Starovoitov
2025-08-12 4:02 ` Xu Kuohai
2025-08-13 13:22 ` Jordan Rome
2025-08-14 13:59 ` Xu Kuohai
2025-08-04 2:20 ` [PATCH bpf-next 2/4] libbpf: ringbuf: Add overwrite ring buffer process Xu Kuohai
2025-08-13 18:21 ` Zvi Effron
2025-08-14 14:10 ` Xu Kuohai
2025-08-14 19:34 ` Eduard Zingerman
2025-08-14 21:20 ` Zvi Effron [this message]
2025-08-22 21:23 ` Andrii Nakryiko
2025-08-23 14:38 ` Xu Kuohai
2025-08-04 2:20 ` [PATCH bpf-next 3/4] selftests/bpf: Add test for overwrite ring buffer Xu Kuohai
2025-08-04 2:21 ` [PATCH bpf-next 4/4] selftests/bpf/benchs: Add overwrite mode bench for rb-libbpf Xu Kuohai
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='CAC1LvL1=61DYMAG=c57LRns++9rHF_thD3Kn=nopUoi8CkPshA@mail.gmail.com' \
--to=zeffron@riotgames.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chen.dylane@linux.dev \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.kelly@crowdstrike.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=mykolal@fb.com \
--cc=paul.chaignon@gmail.com \
--cc=sdf@fomichev.me \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=willemb@google.com \
--cc=xukuohai@huaweicloud.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;
as well as URLs for NNTP newsgroup(s).