[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160106082106.GU6373@twins.programming.kicks-ass.net>
Date: Wed, 6 Jan 2016 09:21:06 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
Cc: ling.ma.program@...il.com, waiman.long@....com, mingo@...hat.com,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
ling.ml@...baba-inc.com
Subject: Re: [RFC PATCH] alispinlock: acceleration from lock integration on
multi-core platform
On Wed, Jan 06, 2016 at 09:16:43AM +0100, Peter Zijlstra wrote:
> On Tue, Jan 05, 2016 at 09:42:27PM +0000, One Thousand Gnomes wrote:
> > > It suffers the typical problems all those constructs do; namely it
> > > wrecks accountability.
> >
> > That's "government thinking" ;-) - for most real users throughput is
> > more important than accountability. With the right API it ought to also
> > be compile time switchable.
>
> Its to do with having been involved with -rt. RT wants to do
> accountability for such things because of PI and sorts.
Also, real people really do care about latency too, very bad worst case
spikes to upset things.
--
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