From: Peter Zijlstra <peterz@infradead.org>
To: Baoquan He <bhe@redhat.com>
Cc: Waiman Long <waiman.long@hp.com>,
mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] locking/rwlocks: clean up of qrwlock
Date: Tue, 6 Jan 2015 11:13:11 +0100 [thread overview]
Message-ID: <20150106101311.GM29390@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150106092542.GB2726@dhcp-16-105.nay.redhat.com>
On Tue, Jan 06, 2015 at 05:25:42PM +0800, Baoquan He wrote:
> Hi all,
>
> Thanks for reviewing.
>
> Do you have any other concerns about this small change?
I just don't see any point in making the code worse for the 1 arch that
actually uses it. If there were other archs using it and for them the
code generation would be negatively impacted (they'd actually generate
more core because of it) it might be worth looking at.
next prev parent reply other threads:[~2015-01-06 10:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 6:00 [PATCH] locking/rwlocks: clean up of qrwlock Baoquan He
2014-12-16 9:01 ` Peter Zijlstra
2014-12-16 15:36 ` Baoquan He
2014-12-17 21:16 ` Waiman Long
2015-01-06 9:25 ` Baoquan He
2015-01-06 10:13 ` Peter Zijlstra [this message]
2015-01-06 12:08 ` Baoquan He
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=20150106101311.GM29390@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=waiman.long@hp.com \
/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