From: Waiman Long <llong@redhat.com>
To: Davidlohr Bueso <dave@stgolabs.net>, tglx@linutronix.de
Cc: peterz@infradead.org, mingo@kernel.org, rostedt@goodmis.org,
bigeasy@linutronix.de, boqun.feng@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip 0/2] locking/rwbase: Two reader optimizations
Date: Mon, 20 Sep 2021 17:54:19 -0400 [thread overview]
Message-ID: <1676b749-3fca-fa67-03e6-7639ef1f5b33@redhat.com> (raw)
In-Reply-To: <20210920052031.54220-1-dave@stgolabs.net>
On 9/20/21 1:20 AM, Davidlohr Bueso wrote:
> Hi,
>
> Patch 1 is a barrier optimization that came up from the reader
> fastpath ordering auditing.
>
> Patch 2 is a resend of the previous broken patch that attempts
> to use wake_q for read_unlock() slowpath.
>
> Tested on v5.15.y-rt. Applies against tip/urgent.
>
> Thanks!
>
> Davidlohr Bueso (2):
> locking/rwbase: Optimize rwbase_read_trylock
> locking/rwbase: Lockless reader waking up a writer
>
> kernel/locking/rtmutex.c | 19 +++++++++++++------
> kernel/locking/rwbase_rt.c | 11 +++++++----
> 2 files changed, 20 insertions(+), 10 deletions(-)
>
> --
> 2.26.2
>
Your patches look good to me.
Acked-by: Waiman Long <longman@redhat.com>
prev parent reply other threads:[~2021-09-20 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 5:20 Davidlohr Bueso
2021-09-20 5:20 ` [PATCH 1/2] locking/rwbase: Optimize rwbase_read_trylock Davidlohr Bueso
2021-10-09 10:07 ` [tip: locking/core] " tip-bot2 for Davidlohr Bueso
2021-09-20 5:20 ` [PATCH 2/2] locking/rwbase: Lockless reader waking up a writer Davidlohr Bueso
2021-09-20 21:54 ` Waiman Long [this message]
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=1676b749-3fca-fa67-03e6-7639ef1f5b33@redhat.com \
--to=llong@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®