From: Stephen Hemminger <stephen@networkplumber.org>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: "Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
<dev@dpdk.org>, "nd" <nd@arm.com>
Subject: Re: [RFC] rwlock: prevent readers from starving writers
Date: Sat, 9 Jul 2022 09:25:28 -0700 [thread overview]
Message-ID: <20220709092528.68397bf0@hermes.local> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D871BB@smartserver.smartshare.dk>
On Sat, 9 Jul 2022 00:04:27 +0200
Morten Brørup <mb@smartsharesystems.com> wrote:
> Always the creative mind, Stephen. :-)
>
> You might consider adding/updating even more comments.
>
> Acked-by: Morten Brørup <mb@smartsharesystems.com>
The motivation is that our work load is reader/writer lock heavy
with small number of threads. Therefore the number of atomic operations
per lock matters, but starving is bad. And any compare-exchange on ARM
is expensive and should be avoided if possible.
The concept here came from this great page.
https://locklessinc.com/articles/locks/
Will add link in next version.
next prev parent reply other threads:[~2022-07-09 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 20:12 [RFC] rwlock: prevent readers from starving writers Stephen Hemminger
2022-07-08 19:22 ` Honnappa Nagarahalli
2022-07-08 22:04 ` Morten Brørup
2022-07-09 16:22 ` Stephen Hemminger
2022-07-09 16:25 ` Stephen Hemminger [this message]
2022-07-19 20:27 ` [PATCH v2] " Stephen Hemminger
2022-07-19 21:52 ` Morten Brørup
2022-07-19 22:33 ` Stephen Hemminger
2022-07-20 6:48 ` Morten Brørup
2022-10-03 10:01 ` David Marchand
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=20220709092528.68397bf0@hermes.local \
--to=stephen@networkplumber.org \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=nd@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.