From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: David Marchand <david.marchand@redhat.com>,
Wathsala Vithanage <wathsala.vithanage@arm.com>
Cc: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Ola Liljedahl <ola.liljedahl@arm.com>,
Dhruv Tripathi <dhruv.tripathi@arm.com>
Subject: RE: [PATCH v2 1/1] ring: safe partial ordering for head/tail update
Date: Mon, 10 Nov 2025 10:25:43 +0000 [thread overview]
Message-ID: <7b9710689ad44caba2c9868967ac97d7@huawei.com> (raw)
In-Reply-To: <CAJFAV8yumnbPjakBAtkoqrZvWCo90F51Ri9Eje44sAmm_S43gw@mail.gmail.com>
Hi David,
>
> Hello Wathsala,
>
> On Mon, 13 Oct 2025 at 20:10, Wathsala Vithanage
> <wathsala.vithanage@arm.com> wrote:
> > > LGTM, though. I think that we also need to make similar changes in
> > > rte_ring_hts_elem_pvt.h and rte_ring_rts_elem_pvt.h:
> > > for CAS use 'acq_rel' order instead of simple 'acquire'.
> > > Let me know would you have a bandwidth to do that.
> >
> > My bad, I forgot those two cases. I will send a v3.
>
> Should we wait for this v3?
> We want to close rc2 this week.
>
Just submitted v3 with discussed extra changes.
Also added fixes, cc to stable, etc.
Hope it still can make 25.11
Wathsala, pls shout or submit v4 if you feel something is missing.
Thanks
Konstantin
next prev parent reply other threads:[~2025-11-10 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 17:41 [PATCH v2 0/1] ring: correct ordering issue in " Wathsala Vithanage
2025-10-02 17:41 ` [PATCH v2 1/1] ring: safe partial ordering for " Wathsala Vithanage
2025-10-08 8:00 ` Konstantin Ananyev
2025-10-13 18:09 ` Wathsala Vithanage
2025-11-06 8:15 ` David Marchand
2025-11-10 10:25 ` Konstantin Ananyev [this message]
2025-11-10 19:13 ` Wathsala Vithanage
2025-11-11 7:48 ` Konstantin Ananyev
2025-11-10 10:17 ` [PATCH v3 0/1] ring: correct ordering issue in " Konstantin Ananyev
2025-11-10 10:17 ` [PATCH v3 1/1] ring: fix unsafe ordering for " Konstantin Ananyev
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=7b9710689ad44caba2c9868967ac97d7@huawei.com \
--to=konstantin.ananyev@huawei.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dhruv.tripathi@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=ola.liljedahl@arm.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 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).