public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Marat Khalili <marat.khalili@huawei.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 0/2] bpf: add xchg and fix rte_bpf_dump
Date: Wed, 04 Feb 2026 12:40:06 +0100	[thread overview]
Message-ID: <9574512.NyiUUSuA9g@thomas> (raw)
In-Reply-To: <20251218170914.7737-1-marat.khalili@huawei.com>

18/12/2025 18:09, Marat Khalili:
> Two patches that are not exectly functionally related, but one depends
> on the other code-wise.
> 
> Atomic exchange is particularly useful since it can be used not just for
> exchange per se, but also as atomic store.
> 
> Incidentally it was discovered that rte_bpf_dump does not support not
> just atomics but also some other instructions.
> 
> v2: Fix CI failure: do not assume in tests that all platforms have JIT.
> 
> Marat Khalili (2):
>   bpf: add atomic xchg support
>   bpf: dump additional instructions

Applied with REGISTER_FAST_TEST updated to the new standard values.



      parent reply	other threads:[~2026-02-04 11:40 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
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   ` Thomas Monjalon [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=9574512.NyiUUSuA9g@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=marat.khalili@huawei.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