From: Stephen Hemminger <stephen@networkplumber.org>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: rwlock with transactional memory
Date: Tue, 19 Jul 2022 13:20:23 -0700 [thread overview]
Message-ID: <20220719132023.1b02bebd@hermes.local> (raw)
The reader writer lock transactional memory appears to turn the rwlock into just a spinlock.
When there are multiple readers, it will think that transaction was impacted.
Kind of want to just drop the TM support from reader writer lock, doubt if anyone uses it.
reply other threads:[~2022-07-19 20:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220719132023.1b02bebd@hermes.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).