From: Will Deacon <will.deacon@arm.com>
To: Waiman Long <Waiman.Long@hp.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Scott J Norton <scott.norton@hp.com>,
Douglas Hatch <doug.hatch@hp.com>
Subject: Re: [PATCH-tip v2 0/2] locking/qrwlock: Improve qrwlock performance
Date: Thu, 16 Jul 2015 16:53:12 +0100 [thread overview]
Message-ID: <20150716155312.GK26390@arm.com> (raw)
In-Reply-To: <1436459543-29126-1-git-send-email-Waiman.Long@hp.com>
Hi Waiman,
On Thu, Jul 09, 2015 at 05:32:21PM +0100, Waiman Long wrote:
> v1->v2:
> - Take out patch 1 which had been merged to tip.
> - Take out patch 4 as the change may impact light load performance
> - Rebased to the latest tip branch
>
> In converting some existing spinlocks to rwlock, it was found that
> the write lock slowpath performance isn't as good as the qspinlock.
> This patch series tries to improve qrwlock performance to close the
> gap between qspinlock and qrwlock.
>
> With this patch series in place, we can start converting some spinlocks
> back to rwlocks where it makes sense and the lock size increase isn't
> a concern.
Both of these patches look fine to me:
Acked-by: Will Deacon <will.deacon@arm.com>
Cheers,
Will
next prev parent reply other threads:[~2015-07-16 15:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 16:32 [PATCH-tip v2 0/2] locking/qrwlock: Improve qrwlock performance Waiman Long
2015-07-09 16:32 ` [PATCH v2 1/2] locking/qrwlock: Reduce reader/writer to reader lock transfer latency Waiman Long
2015-07-09 16:32 ` Waiman Long
2015-07-09 20:52 ` Davidlohr Bueso
2015-07-10 1:10 ` Waiman Long
2015-07-09 16:32 ` [PATCH v2 2/2] locking/qrwlock: Reduce writer to writer " Waiman Long
2015-07-09 16:32 ` Waiman Long
2015-07-09 22:04 ` [PATCH-tip v2 0/2] locking/qrwlock: Improve qrwlock performance Davidlohr Bueso
2015-07-09 22:04 ` Davidlohr Bueso
2015-07-10 1:16 ` Waiman Long
2015-07-16 15:53 ` Will Deacon [this message]
2015-07-16 15:53 ` Will Deacon
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=20150716155312.GK26390@arm.com \
--to=will.deacon@arm.com \
--cc=Waiman.Long@hp.com \
--cc=arnd@arndb.de \
--cc=doug.hatch@hp.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=scott.norton@hp.com \
--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;
as well as URLs for NNTP newsgroup(s).