From: Waiman Long <waiman.long@hp.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: walken@google.com, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>, Rik van Riel <riel@redhat.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
George Spelvin <linux@horizon.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
"Chandramouleeswaran, Aswin" <aswin@hp.com>,
"Norton, Scott J" <scott.norton@hp.com>
Subject: Re: [PATCH v4 1/3] qrwlock: A queue read/write lock implementation
Date: Thu, 24 Oct 2013 10:12:55 -0400 [thread overview]
Message-ID: <52692AE7.3060701@hp.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1310241207500.4983@ionos.tec.linutronix.de>
On 10/24/2013 06:14 AM, Thomas Gleixner wrote:
> On Wed, 23 Oct 2013, Waiman Long wrote:
>> On 10/23/2013 08:00 AM, walken@google.com wrote:
>>>> + /*
>>>> + * Wait until the next one in queue set up the next field
>>>> + */
>>>> + while (likely(!(next = ACCESS_ONCE(node->next))))
>>>> + cpu_relax();
>>>> + /*
>>>> + * The next one in queue is now at the head
>>>> + */
>>>> +notify_next:
>>>> + barrier();
>>>> + ACCESS_ONCE(next->wait) = false;
>>>> + smp_wmb();
>>>> +}
>>> I believe this could be unified with mspin_lock() / mspin_unlock() in
>>> kernel/mutex.c ? (there is already talk of extending these functions
>>> to be used by rwsem for adaptive spinning as well...)
>> It probably can, but the unification can wait until the code are in.
> The unification has to be done as a part of this series. Cleanups are
> part of the development process of new code and not an optional
> feature.
>
> Thanks,
>
> tglx
>
There is an outstanding rwsem patch series that is doing the
unification. I am waiting for that patch series to be at least in a tip
or linux-next branch before doing the unification. Otherwise, it will
cause merge conflict.
-Longman
next prev parent reply other threads:[~2013-10-24 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 14:09 [PATCH v4 0/3] qrwlock: Introducing a queue read/write lock implementation Waiman Long
2013-10-02 14:09 ` [PATCH v4 1/3] qrwlock: A " Waiman Long
2013-10-02 14:09 ` Waiman Long
2013-10-23 12:00 ` walken
2013-10-23 12:00 ` walken
2013-10-23 16:58 ` Waiman Long
2013-10-24 10:14 ` Thomas Gleixner
2013-10-24 14:12 ` Waiman Long [this message]
2013-10-24 16:24 ` Tim Chen
2013-10-02 14:09 ` Waiman Long
2013-10-02 14:09 ` [PATCH v4 2/3] qrwlock x86: Enable x86 to use queue read/write lock Waiman Long
2013-10-02 14:09 ` Waiman Long
2013-10-02 14:09 ` [PATCH v4 3/3] qrwlock: Enable fair " Waiman Long
2013-10-02 14:09 ` Waiman Long
2013-10-02 15:19 ` [PATCH v4 0/3] qrwlock: Introducing a queue read/write lock implementation Peter Zijlstra
2013-10-02 15:25 ` Ingo Molnar
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=52692AE7.3060701@hp.com \
--to=waiman.long@hp.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=arnd@arndb.de \
--cc=aswin@hp.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--cc=rostedt@goodmis.org \
--cc=scott.norton@hp.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=walken@google.com \
--cc=x86@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).