From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "Puranjay Mohan" <puranjay@kernel.org>, <bpf@vger.kernel.org>
Cc: "Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Kumar Kartikeya Dwivedi" <memxor@gmail.com>,
"Song Liu" <song@kernel.org>,
"Yonghong Song" <yonghong.song@linux.dev>
Subject: Re: [PATCH bpf-next 2/2] selftests/bpf: Test fetching AND/OR/XOR atomics in arena
Date: Wed, 23 Sep 2026 22:11:19 +0000 [thread overview]
Message-ID: <DLN1GM1DR3L8.1B0FXOU9BB33H@gmail.com> (raw)
In-Reply-To: <20260923165301.3463007-3-puranjay@kernel.org>
On Wed, Sep 23, 2026 at 09:53 AM Puranjay Mohan <puranjay@kernel.org> wrote:
> -#ifdef __BPF_FEATURE_ATOMIC_MEM_ORDERING
> - __c11_atomic_fetch_and(&and64_value, 0x011ull << 32, memory_order_relaxed);
> - __c11_atomic_fetch_and(&and32_value, 0x011, memory_order_relaxed);
> -#else
> - __sync_fetch_and_and(&and64_value, 0x011ull << 32);
> - __sync_fetch_and_and(&and32_value, 0x011);
> -#endif
> + and64_result = __sync_fetch_and_and(&and64_value, 0x011ull << 32);
> + and32_result = __sync_fetch_and_and(&and32_value, 0x011);
These were the only tests of non-fetching and/or/xor in arena.
Pls keep them and add the fetching ones next to them.
prev parent reply other threads:[~2026-09-23 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 16:52 [PATCH bpf-next 0/2] bpf, x86: Support fetching AND/OR/XOR atomics in arena Puranjay Mohan
2026-09-23 16:52 ` [PATCH bpf-next 1/2] " Puranjay Mohan
2026-09-23 18:03 ` bot+bpf-ci
2026-09-23 22:10 ` Alexei Starovoitov
2026-09-23 16:53 ` [PATCH bpf-next 2/2] selftests/bpf: Test " Puranjay Mohan
2026-09-23 22:11 ` Alexei Starovoitov [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=DLN1GM1DR3L8.1B0FXOU9BB33H@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=puranjay@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.