From: Stephen Hemminger <stephen@networkplumber.org>
To: Marat Khalili <marat.khalili@huawei.com>
Cc: <dev@dpdk.org>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>,
Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: Re: [PATCH v2 1/2] bpf: add atomic xchg support
Date: Mon, 29 Dec 2025 10:10:41 -0800 [thread overview]
Message-ID: <20251229101041.5245f1ab@phoenix.local> (raw)
In-Reply-To: <20251218170914.7737-2-marat.khalili@huawei.com>
On Thu, 18 Dec 2025 17:09:12 +0000
Marat Khalili <marat.khalili@huawei.com> wrote:
> Add support for BPF atomic xchg instruction, and tests for it. This
> instruction can be produced using compiler intrinsics.
>
> Signed-off-by: Marat Khalili <marat.khalili@huawei.com>
> ---
Should make sure that CMP32 and all the other current instructions
are also covered. See kernel docs for list.
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2025-12-29 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 17:20 [PATCH 0/2] bpf: add xchg and fix rte_bpf_dump Marat Khalili
2025-12-17 17:20 ` [PATCH 1/2] bpf: add atomic xchg support Marat Khalili
2025-12-17 17:20 ` [PATCH 2/2] bpf: dump additional instructions Marat Khalili
2025-12-18 17:09 ` [PATCH v2 0/2] bpf: add xchg and fix rte_bpf_dump Marat Khalili
2025-12-18 17:09 ` [PATCH v2 1/2] bpf: add atomic xchg support Marat Khalili
2025-12-19 13:03 ` Konstantin Ananyev
2025-12-29 18:10 ` Stephen Hemminger [this message]
2025-12-18 17:09 ` [PATCH v2 2/2] bpf: dump additional instructions Marat Khalili
2025-12-19 13:04 ` Konstantin Ananyev
2026-02-04 11:40 ` [PATCH v2 0/2] bpf: add xchg and fix rte_bpf_dump Thomas Monjalon
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=20251229101041.5245f1ab@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=marat.khalili@huawei.com \
--cc=wathsala.vithanage@arm.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 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.