From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>
Cc: linux-kernel@vger.kernel.org, Hillf Danton <hdanton@sina.com>,
Waiman Long <longman@redhat.com>
Subject: [PATCH-tip v2 0/3] locking/rwsem: Miscellaneous rwsem enhancements
Date: Thu, 16 Feb 2023 16:09:30 -0500 [thread overview]
Message-ID: <20230216210933.1169097-1-longman@redhat.com> (raw)
v2:
- Break out some code refactoring into a separate patch.
- Move the early handoff code from rwsem_wake() to rwsem_mark_wake() to
cover all wakeup conditions as suggested by PeterZ.
- Simplify the all reader wake up patch.
The second patch in this series is similar to patch 4 of the v7 patch
series [1]. So it should provide similar performance benefit. Patch 3
is another minor enhancement about reader wakeup for some specific
use cases.
[1] https://lore.kernel.org/lkml/20230126003628.365092-1-longman@redhat.com/
Waiman Long (3):
locking/rwsem: Minor code refactoring in rwsem_mark_wake()
locking/rwsem: Enable early rwsem writer lock handoff
locking/rwsem: Wake up all readers for wait queue waker
kernel/locking/lock_events_list.h | 1 +
kernel/locking/rwsem.c | 133 ++++++++++++++++++++++--------
2 files changed, 99 insertions(+), 35 deletions(-)
--
2.31.1
next reply other threads:[~2023-02-16 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 21:09 Waiman Long [this message]
2023-02-16 21:09 ` [PATCH v2 1/3] locking/rwsem: Minor code refactoring in rwsem_mark_wake() Waiman Long
2023-02-16 21:09 ` [PATCH v2 2/3] locking/rwsem: Enable early rwsem writer lock handoff Waiman Long
2023-02-17 5:24 ` Boqun Feng
2023-02-17 14:25 ` Waiman Long
2023-02-23 12:32 ` Peter Zijlstra
2023-02-23 14:16 ` Waiman Long
2023-02-16 21:09 ` [PATCH v2 3/3] locking/rwsem: Wake up all readers for wait queue waker Waiman Long
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=20230216210933.1169097-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=boqun.feng@gmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.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).