[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130416091259.GC9569@gmail.com>
Date:	Tue, 16 Apr 2013 11:12:59 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Waiman Long <Waiman.Long@...com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	David Howells <dhowells@...hat.com>,
	Dave Jones <davej@...hat.com>,
	Clark Williams <williams@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, x86@...nel.org,
	linux-arch@...r.kernel.org,
	"Chandramouleeswaran, Aswin" <aswin@...com>,
	Davidlohr Bueso <davidlohr.bueso@...com>,
	"Norton, Scott J" <scott.norton@...com>,
	Rik van Riel <riel@...hat.com>
Subject: Re: [PATCH 0/3 v2] mutex: Improve mutex performance by doing less
 atomic-ops & better spinning
* Waiman Long <Waiman.Long@...com> wrote:
> [...]
> 
> Patches 2 improves the mutex spinning process by reducing contention among the 
> spinners when competing for the mutex. This is done by using a MCS lock to put 
> the spinners in a queue so that only the first spinner will try to acquire the 
> mutex when it is available. This patch showed significant performance 
> improvement of +30% on the AIM7 fserver and new_fserver workload.
Ok, that's really nice - and this approach has no arbitrary limits/tunings in it.
Do you have a performance comparison to your first series (patches 1+2+3 IIRC) - 
how does this new series with MCS locking compare to the best previous result from 
that old series? Do we now achieve that level of performance?
Thanks,
	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Powered by blists - more mailing lists
 
