From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
Diogo Behrens <diogo.behrens@huawei.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] librte_eal: fix mcslock hang on weak memory
Date: Mon, 23 Nov 2020 18:16:44 +0000 [thread overview]
Message-ID: <DBAPR08MB581498AE76D1F3FE6E28525498FC0@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20201123074403.054d08aa@hermes.local>
<snip>
>
> Has anyone investigated later developments in concurrency?
> While researching MCS Lock discovered this quote:
> https://mfukar.github.io/2017/09/26/mcs.html
> Luckily, we don’t have to worry about this very much. MCS locks
> right now are mostly a teaching tool, and have mostly been superseded
> by:
>
> CLH locks: Craig, Landin, and Hagersten locks replace the explicit
> queue for a logical queue
> K42 locks: On-stack information is used instead of keeping a thread-
> local
> queue node around.
> A similar idea is used by the stack-lock algorithm.
I have not looked at these. I have looked briefly at a NUMA aware locks.
>
> Note: K42 locks are patented by IBM.
next prev parent reply other threads:[~2020-11-23 18:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 9:20 Diogo Behrens
2020-08-26 10:17 ` Phil Yang
2020-08-27 8:56 ` Diogo Behrens
2020-08-28 9:19 ` Phil Yang
2020-08-31 18:45 ` Honnappa Nagarahalli
2020-10-06 21:49 ` Thomas Monjalon
2020-10-07 9:55 ` Diogo Behrens
2020-10-20 11:56 ` Thomas Monjalon
2020-10-20 21:49 ` Honnappa Nagarahalli
2020-11-22 18:07 ` Thomas Monjalon
2020-11-23 15:06 ` Honnappa Nagarahalli
2020-11-23 15:44 ` Stephen Hemminger
2020-11-23 18:16 ` Honnappa Nagarahalli [this message]
2020-11-23 18:29 ` Honnappa Nagarahalli
2020-11-23 19:36 ` Stephen Hemminger
2020-11-25 4:50 ` Honnappa Nagarahalli
2020-11-25 8:41 ` Diogo Behrens
2020-11-25 14:16 ` 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=DBAPR08MB581498AE76D1F3FE6E28525498FC0@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=diogo.behrens@huawei.com \
--cc=nd@arm.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).