[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160112135016.247c6ca5@lxorguk.ukuu.org.uk>
Date: Tue, 12 Jan 2016 13:50:16 +0000
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Ling Ma <ling.ma.program@...il.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Waiman Long <waiman.long@....com>, mingo@...hat.com,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
Ling <ling.ml@...baba-inc.com>
Subject: Re: [RFC PATCH] alispinlock: acceleration from lock integration on
multi-core platform
On Sat, 9 Jan 2016 06:44:15 +0800
Ling Ma <ling.ma.program@...il.com> wrote:
> The attachment (alispinlock.tar.bz2) includes original spinlock and
> alispinlock ,
> we compare them on 70 cores based on kernel 4.3, the alispinlock can
> improve performance upto 3x.
>
> the link: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1035940.html
> indicates when we introduce the idea for real application(user space
> application caused the bottle neck from kernel spinlock )
> the spinlock performance is improved by 1.9x (perf top -d1 also tell
> us the spinlock cost time is reduced from 25% to 15%).
>
> Appreciate your comments
So this has not been applied to actual real kernel locks (ie converted
some of the hot kernel locks to it) and then benchmarked with a real
world workload. This is just for the theoretical locking overhead ?
Alan
Powered by blists - more mailing lists