From: "H. Peter Anvin" <hpa@zytor.com>
To: Tim Chen <tim.c.chen@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
linux-arch@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Waiman Long <waiman.long@hp.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Alex Shi <alex.shi@linaro.org>, Andi Kleen <andi@firstfloor.org>,
Michel Lespinasse <walken@google.com>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
Matthew R Wilcox <matthew.r.wilcox@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rik van Riel <riel@redhat.com>,
Peter Hurley <peter@hurleysoftware.com>,
"Paul E.McKenney" <paulmck@linux.vnet.ibm.com>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
George Spelvin <linux@horizon.com>, Arnd Bergmann <arnd@arndb.de>,
Aswin Chandramouleeswaran <aswin@hp.com>
Subject: Re: [PATCH v3 0/4] MCS Lock: MCS lock code cleanup and optimizations
Date: Wed, 06 Nov 2013 13:42:34 -0800 [thread overview]
Message-ID: <527AB7CA.4020502@zytor.com> (raw)
In-Reply-To: <1383773816.11046.352.camel@schen9-DESK>
On 11/06/2013 01:36 PM, Tim Chen wrote:
> In this patch series, we separated out the MCS lock code which was
> previously embedded in the mutex.c. This allows for easier reuse of
> MCS lock in other places like rwsem and qrwlock. We also did some micro
> optimizations and barrier cleanup.
>
> This patches were previously part of the rwsem optimization patch series
> but now we spearate them out.
>
> Tim Chen
Perhaps I'm missing something here, but what is MCS lock and what is the
value?
-hpa
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Tim Chen <tim.c.chen@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
linux-arch@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Waiman Long <waiman.long@hp.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Alex Shi <alex.shi@linaro.org>, Andi Kleen <andi@firstfloor.org>,
Michel Lespinasse <walken@google.com>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
Matthew R Wilcox <matthew.r.wilcox@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rik van Riel <riel@redhat.com>,
Peter Hurley <peter@hurleysoftware.com>,
"Paul E.McKenney" <paulmck@linux.vnet.ibm.com>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
George Spelvin <linux@horizon.com>, Arnd Bergmann <arnd@arndb.de>,
Aswin Chandramouleeswaran <aswin@hp.com>,
Scott J Norton <scott.norton@hp.com>,
Will Deacon <will.deacon@arm.com>,
"Figo.zhang" <figo1802@gmail.com>
Subject: Re: [PATCH v3 0/4] MCS Lock: MCS lock code cleanup and optimizations
Date: Wed, 06 Nov 2013 13:42:34 -0800 [thread overview]
Message-ID: <527AB7CA.4020502@zytor.com> (raw)
Message-ID: <20131106214234.1hTJd6NGU7dCmzH_8bHfXoOLQsxS6GP3_xUZ9SCzns8@z> (raw)
In-Reply-To: <1383773816.11046.352.camel@schen9-DESK>
On 11/06/2013 01:36 PM, Tim Chen wrote:
> In this patch series, we separated out the MCS lock code which was
> previously embedded in the mutex.c. This allows for easier reuse of
> MCS lock in other places like rwsem and qrwlock. We also did some micro
> optimizations and barrier cleanup.
>
> This patches were previously part of the rwsem optimization patch series
> but now we spearate them out.
>
> Tim Chen
Perhaps I'm missing something here, but what is MCS lock and what is the
value?
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Tim Chen <tim.c.chen@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-mm <linux-mm@kvack.org>,
linux-arch@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Waiman Long <waiman.long@hp.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Alex Shi <alex.shi@linaro.org>, Andi Kleen <andi@firstfloor.org>,
Michel Lespinasse <walken@google.com>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
Matthew R Wilcox <matthew.r.wilcox@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rik van Riel <riel@redhat.com>,
Peter Hurley <peter@hurleysoftware.com>,
"Paul E.McKenney" <paulmck@linux.vnet.ibm.com>,
Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
George Spelvin <linux@horizon.com>, Arnd Bergmann <arnd@arndb.de>,
Aswin Chandramouleeswaran <aswin@hp.com>,
Scott J Norton <scott.norton@hp.com>,
Will Deacon <will.deacon@arm.com>,
"Figo.zhang" <figo1802@gmail.com>
Subject: Re: [PATCH v3 0/4] MCS Lock: MCS lock code cleanup and optimizations
Date: Wed, 06 Nov 2013 13:42:34 -0800 [thread overview]
Message-ID: <527AB7CA.4020502@zytor.com> (raw)
In-Reply-To: <1383773816.11046.352.camel@schen9-DESK>
On 11/06/2013 01:36 PM, Tim Chen wrote:
> In this patch series, we separated out the MCS lock code which was
> previously embedded in the mutex.c. This allows for easier reuse of
> MCS lock in other places like rwsem and qrwlock. We also did some micro
> optimizations and barrier cleanup.
>
> This patches were previously part of the rwsem optimization patch series
> but now we spearate them out.
>
> Tim Chen
Perhaps I'm missing something here, but what is MCS lock and what is the
value?
-hpa
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-11-06 21:42 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1383771175.git.tim.c.chen@linux.intel.com>
2013-11-06 21:36 ` [PATCH v3 0/4] MCS Lock: MCS lock code cleanup and optimizations Tim Chen
2013-11-06 21:36 ` Tim Chen
2013-11-06 21:36 ` Tim Chen
2013-11-06 21:41 ` Davidlohr Bueso
2013-11-06 21:41 ` Davidlohr Bueso
2013-11-06 23:55 ` Tim Chen
2013-11-06 23:55 ` Tim Chen
2013-11-06 21:42 ` H. Peter Anvin [this message]
2013-11-06 21:42 ` H. Peter Anvin
2013-11-06 21:42 ` H. Peter Anvin
2013-11-06 21:59 ` Michel Lespinasse
2013-11-06 21:59 ` Michel Lespinasse
2013-11-06 21:59 ` Michel Lespinasse
2013-11-06 21:37 ` [PATCH v3 1/5] MCS Lock: Restructure the MCS lock defines and locking code into its own file Tim Chen
2013-11-06 21:37 ` Tim Chen
2013-11-06 21:37 ` Tim Chen
2013-11-06 21:37 ` [PATCH v3 2/5] MCS Lock: optimizations and extra comments Tim Chen
2013-11-06 21:37 ` Tim Chen
2013-11-06 21:37 ` Tim Chen
2013-11-06 21:47 ` Tim Chen
2013-11-06 21:47 ` Tim Chen
2013-11-06 21:47 ` Tim Chen
2013-11-06 21:37 ` [PATCH v3 3/5] MCS Lock: Barrier corrections Tim Chen
2013-11-06 21:37 ` Tim Chen
2013-11-06 21:37 ` Tim Chen
2013-11-07 1:39 ` Linus Torvalds
2013-11-07 1:39 ` Linus Torvalds
2013-11-07 4:29 ` Waiman Long
2013-11-07 4:29 ` Waiman Long
2013-11-07 8:13 ` Ingo Molnar
2013-11-07 8:13 ` Ingo Molnar
2013-11-07 8:22 ` Linus Torvalds
2013-11-07 8:22 ` Linus Torvalds
2013-11-07 8:25 ` Ingo Molnar
2013-11-07 8:25 ` Ingo Molnar
2013-11-07 9:55 ` Michel Lespinasse
2013-11-07 9:55 ` Michel Lespinasse
2013-11-07 9:55 ` Michel Lespinasse
2013-11-07 12:06 ` Linus Torvalds
2013-11-07 12:06 ` Linus Torvalds
2013-11-07 12:50 ` Michel Lespinasse
2013-11-07 12:50 ` Michel Lespinasse
2013-11-07 12:50 ` Michel Lespinasse
2013-11-07 14:31 ` Paul E. McKenney
2013-11-07 14:31 ` Paul E. McKenney
2013-11-07 14:31 ` Paul E. McKenney
2013-11-07 19:59 ` Michel Lespinasse
2013-11-07 19:59 ` Michel Lespinasse
2013-11-07 19:59 ` Michel Lespinasse
2013-11-07 21:15 ` Tim Chen
2013-11-07 21:15 ` Tim Chen
2013-11-07 21:15 ` Tim Chen
2013-11-07 22:21 ` Peter Zijlstra
2013-11-07 22:21 ` Peter Zijlstra
2013-11-07 22:21 ` Peter Zijlstra
2013-11-07 22:43 ` Michel Lespinasse
2013-11-07 22:43 ` Michel Lespinasse
2013-11-07 22:43 ` Michel Lespinasse
2013-11-08 1:16 ` Tim Chen
2013-11-08 1:16 ` Tim Chen
2013-11-08 1:16 ` Tim Chen
2013-11-06 21:37 ` [PATCH v3 4/5] MCS Lock: Make mcs_spinlock.h includable in other files Tim Chen
2013-11-06 21:37 ` Tim Chen
2013-11-06 21:37 ` Tim Chen
2013-11-06 21:41 ` Tim Chen
2013-11-06 21:41 ` Tim Chen
2013-11-06 21:41 ` Tim Chen
2013-11-06 21:37 ` [PATCH v3 5/5] MCS Lock: Allow architecture specific memory barrier in lock/unlock Tim Chen
2013-11-06 21:37 ` Tim Chen
2013-11-06 21:37 ` Tim Chen
2013-11-06 21:42 ` Tim Chen
2013-11-06 21:42 ` Tim Chen
2013-11-06 21:42 ` Tim Chen
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=527AB7CA.4020502@zytor.com \
--to=hpa@zytor.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@linaro.org \
--cc=andi@firstfloor.org \
--cc=arnd@arndb.de \
--cc=aswin@hp.com \
--cc=dave.hansen@intel.com \
--cc=davidlohr.bueso@hp.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@horizon.com \
--cc=matthew.r.wilcox@intel.com \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peter@hurleysoftware.com \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=waiman.long@hp.com \
--cc=walken@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.