[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1373273368.30325.7.camel@marge.simpson.net>
Date: Mon, 08 Jul 2013 10:49:28 +0200
From: Mike Galbraith <efault@....de>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Michael Wang <wangyun@...ux.vnet.ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>, Alex Shi <alex.shi@...el.com>,
Namhyung Kim <namhyung@...nel.org>,
Paul Turner <pjt@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Nikunj A. Dadhania" <nikunj@...ux.vnet.ibm.com>,
Ram Pai <linuxram@...ibm.com>
Subject: Re: [PATCH] sched: smart wake-affine
On Mon, 2013-07-08 at 10:21 +0200, Peter Zijlstra wrote:
> On Sun, Jul 07, 2013 at 08:43:25AM +0200, Mike Galbraith wrote:
> > On Fri, 2013-07-05 at 14:16 +0800, Michael Wang wrote:
> >
> > > PeterZ has suggested some optimization which I sent out yesterday, I
> > > suppose they haven't been included into this test yet, correct?
> >
> > No, that was with both v3 patches applied. hackbench -l 1000 delta
> > tracked to next pull/build fwiw, but I don't see anything noteworthy
> > elsewhere, so I'm filing it under "tasks/core ~= zillion ~= hohum".
>
> OK, I'll apply the patches, we'll see what happens. If there significant
> fallout we'll immediately have more information anyway ;-)
Yup. It's a repeatable oddity on my box, but it doesn't even track to
itself when using different hackbench parameters. All I can really
conclude from test results is "golly, changing stuff affects stuff" :)
-Mike
--
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