[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140211071700.GH27965@twins.programming.kicks-ass.net>
Date: Tue, 11 Feb 2014 08:17:00 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, Jason Low <jason.low2@...com>,
Waiman Long <waiman.long@...com>, mingo@...nel.org,
paulmck@...ux.vnet.ibm.com, torvalds@...ux-foundation.org,
tglx@...utronix.de, riel@...hat.com, davidlohr@...com,
hpa@...or.com, andi@...stfloor.org, aswin@...com,
scott.norton@...com, chegu_vinod@...com
Subject: Re: [PATCH 0/8] locking/core patches
On Mon, Feb 10, 2014 at 03:02:30PM -0800, Andrew Morton wrote:
> On Mon, 10 Feb 2014 20:58:20 +0100 Peter Zijlstra <peterz@...radead.org> wrote:
>
> > Hi all,
> >
> > I would propose merging the following patches...
> >
> > The first set is mostly from Jason and tweaks the mutex adaptive
> > spinning, AIM7 throughput numbers:
> >
Jobs/min/ Jobs/sec/ Time: Time: Time: Time: Running child time
Forks Jobs/min child child parent childU childS std_dev JTI :max :min
> > PRE: 100 2000.04 21564.90 2721.29 311.99 3.12 0.01 0.00 99
> > POST: 100 2000.04 42603.85 5142.80 311.99 3.12 0.00 0.00 99
>
> What do these columns represent? I'm guessing the large improvement
> was in context switches?
I pasted the header from reaim above; I'm not entirely sure what the
bloody thing does and I hate that it takes hours to get these numbers :/
Bloody stupid benchmark if you ask me.
--
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