From: Anton Protopopov <aspsk@isovalent.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Anton Protopopov <a.s.protopopov@gmail.com>,
bpf@vger.kernel.org, Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH bpf-next 0/4] likely/unlikely for bpf_helpers
Date: Mon, 31 Mar 2025 20:38:41 +0000 [thread overview]
Message-ID: <Z+r9UcPhDyikP48+@mail.gmail.com> (raw)
In-Reply-To: <CAEf4BzaTf-SKBW8j7Y_D81Y4j+MB76Bn0xBRr0YJdv+B7aWfTQ@mail.gmail.com>
On 25/03/31 01:12PM, Andrii Nakryiko wrote:
> On Mon, Mar 31, 2025 at 1:08 AM Anton Protopopov
> <a.s.protopopov@gmail.com> wrote:
> >
> > Andrii suggested to send this piece with small fixes
> > separately from the insn set rfc.
> >
> > The first patch fixes a comment in <linux/bpf.h>, and the latter
> > three patches add likely/unlikely macros to <bph/bpf_helpers.h>.
> > The reason there are three patches and not one is to separate
> > libbpf changes such that userspace libbpf can be updated more
> > easily, and the order is such that each commit can be built.
> >
> > Anton Protopopov (4):
> > bpf: fix a comment describing bpf_attr
> > selftests/bpf: add guard macros around likely/unlikely
> > libbpf: add likely/unlikely macros
> > selftests/bpf: remove likely/unlikely definitions
>
> let's just collapse the last 3 patches into one? libbpf sync process
> will be totally fine with that.
Thanks, I've squashed them in v2.
> pw-bot: cr
>
> >
> > include/uapi/linux/bpf.h | 2 +-
> > tools/include/uapi/linux/bpf.h | 2 +-
> > tools/lib/bpf/bpf_helpers.h | 8 ++++++++
> > tools/testing/selftests/bpf/bpf_arena_spin_lock.h | 3 ---
> > tools/testing/selftests/bpf/progs/iters.c | 2 --
> > 5 files changed, 10 insertions(+), 7 deletions(-)
> >
> > --
> > 2.34.1
> >
prev parent reply other threads:[~2025-03-31 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 8:13 [PATCH bpf-next 0/4] likely/unlikely for bpf_helpers Anton Protopopov
2025-03-31 8:13 ` [PATCH bpf-next 1/4] bpf: fix a comment describing bpf_attr Anton Protopopov
2025-03-31 8:13 ` [PATCH bpf-next 2/4] selftests/bpf: add guard macros around likely/unlikely Anton Protopopov
2025-03-31 8:13 ` [PATCH bpf-next 3/4] libbpf: add likely/unlikely macros Anton Protopopov
2025-03-31 8:13 ` [PATCH bpf-next 4/4] selftests/bpf: remove likely/unlikely definitions Anton Protopopov
2025-03-31 20:12 ` [PATCH bpf-next 0/4] likely/unlikely for bpf_helpers Andrii Nakryiko
2025-03-31 20:38 ` Anton Protopopov [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=Z+r9UcPhDyikP48+@mail.gmail.com \
--to=aspsk@isovalent.com \
--cc=a.s.protopopov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
/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