From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: Wathsala Vithanage <wathsala.vithanage@arm.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Ola Liljedahl <ola.liljedahl@arm.com>,
"vattunuru@marvell.com" <vattunuru@marvell.com>
Subject: RE: [PATCH 1/1] eal: correct memory ordering in MCS lock
Date: Mon, 3 Nov 2025 18:06:05 +0000 [thread overview]
Message-ID: <d63bc45cb32848299574333fed5e5406@huawei.com> (raw)
In-Reply-To: <b435dd1d-c56f-4d56-9f73-30ee1ec99eac@arm.com>
>
> On 11/3/25 11:07, Stephen Hemminger wrote:
> > On Mon, 3 Nov 2025 09:12:39 -0600
> > Wathsala Vithanage <wathsala.vithanage@arm.com> wrote:
> >
> >> MCS lock is broken, it's just a matter of time it will run into a deadlock.
> >>
> >> drivers/dma/cnxk is a user of MCS lock.
> > I am surprised that a driver would use mcslock.
> > MCSlock is targeted at case of large number of CPU's with lots of contention.
> > It will likely be slower than spinlock or ticketlock for the use case of driver.
> It appears in |drivers/dma/cnxk/cnxk_dmadev_fp.c|, perhaps the
> maintainer can clarify.
>
If MCS lock is really broken, it needs to be fixed anyway.
It might be used by other third-party libs/apps that do use on DPDK.
next prev parent reply other threads:[~2025-11-03 18:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 18:47 [PATCH 1/1] eal: correct memory ordering in MCS lock Wathsala Vithanage
2025-11-03 15:12 ` Wathsala Vithanage
2025-11-03 17:07 ` Stephen Hemminger
2025-11-03 17:30 ` Wathsala Vithanage
2025-11-03 18:06 ` Konstantin Ananyev [this message]
2025-11-03 18:47 ` Wathsala Vithanage
2025-11-03 18:48 ` Stephen Hemminger
2025-11-03 19:13 ` Wathsala Vithanage
2025-11-04 8:18 ` Konstantin Ananyev
2025-11-05 19:39 ` Ola Liljedahl
2025-11-06 7:48 ` Konstantin Ananyev
2025-11-06 14:10 ` Ola Liljedahl
2025-11-03 23:48 ` Stephen Hemminger
2025-11-04 23:30 ` Wathsala Vithanage
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=d63bc45cb32848299574333fed5e5406@huawei.com \
--to=konstantin.ananyev@huawei.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=ola.liljedahl@arm.com \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.org \
--cc=vattunuru@marvell.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.