From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <longman@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, Davidlohr Bueso <dave@stgolabs.net>,
Phil Auld <pauld@redhat.com>
Subject: Re: [PATCH v2 0/5] locking/rwsem: Rework reader optimistic spinning
Date: Tue, 8 Dec 2020 18:02:33 +0100 [thread overview]
Message-ID: <20201208170233.GG2414@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <77f74f7f-f090-ef3f-11ec-62bc89bd9a83@redhat.com>
On Tue, Dec 08, 2020 at 11:33:38AM -0500, Waiman Long wrote:
> On 12/8/20 9:57 AM, Peter Zijlstra wrote:
> > On Fri, Nov 20, 2020 at 11:14:11PM -0500, Waiman Long wrote:
> > > Waiman Long (5):
> > > locking/rwsem: Pass the current atomic count to
> > > rwsem_down_read_slowpath()
> > > locking/rwsem: Prevent potential lock starvation
> > > locking/rwsem: Enable reader optimistic lock stealing
> > > locking/rwsem: Wake up all waiting readers if RWSEM_WAKE_READ_OWNED
> > > locking/rwsem: Remove reader optimistic spinning
> > So I've munged the lot onto the other rwsem patches and skipped #4, I've
> > not even boot tested them (will go do so shortly).
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
> >
> I have checked the four patches in your locking/core branch. They look good
> to me. Are you planning to push the branch to tip soon so that it can be
> ready for the next merge window?
Yeah, provided the robots don't hate on it more than already reported.
next prev parent reply other threads:[~2020-12-08 17:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 4:14 [PATCH v2 0/5] locking/rwsem: Rework reader optimistic spinning Waiman Long
2020-11-21 4:14 ` [PATCH v2 1/5] locking/rwsem: Pass the current atomic count to rwsem_down_read_slowpath() Waiman Long
2020-12-09 18:38 ` [tip: locking/core] " tip-bot2 for Waiman Long
2020-11-21 4:14 ` [PATCH v2 2/5] locking/rwsem: Prevent potential lock starvation Waiman Long
2020-11-26 8:12 ` [locking/rwsem] 25d0c60b0e: vm-scalability.throughput 316.2% improvement kernel test robot
2020-12-09 18:38 ` [tip: locking/core] locking/rwsem: Prevent potential lock starvation tip-bot2 for Waiman Long
2020-11-21 4:14 ` [PATCH v2 3/5] locking/rwsem: Enable reader optimistic lock stealing Waiman Long
2020-12-09 18:38 ` [tip: locking/core] " tip-bot2 for Waiman Long
2020-11-21 4:14 ` [PATCH v2 4/5] locking/rwsem: Wake up all waiting readers if RWSEM_WAKE_READ_OWNED Waiman Long
2020-11-24 3:15 ` [locking/rwsem] c9847a7f94: aim7.jobs-per-min -91.8% regression kernel test robot
2020-11-21 4:14 ` [PATCH v2 5/5] locking/rwsem: Remove reader optimistic spinning Waiman Long
2020-11-23 15:53 ` [locking/rwsem] 10a59003d2: unixbench.score -25.5% regression kernel test robot
2020-11-23 19:28 ` Waiman Long
2020-12-08 3:56 ` [PATCH v2 5/5] locking/rwsem: Remove reader optimistic spinning Davidlohr Bueso
2020-12-08 10:07 ` Peter Zijlstra
2020-12-08 15:29 ` Waiman Long
2020-12-09 18:38 ` [tip: locking/core] " tip-bot2 for Waiman Long
2020-12-08 14:57 ` [PATCH v2 0/5] locking/rwsem: Rework " Peter Zijlstra
2020-12-08 16:33 ` Waiman Long
2020-12-08 17:02 ` Peter Zijlstra [this message]
2020-12-08 17:30 ` 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=20201208170233.GG2414@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--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