[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1159574473.3286.83.camel@localhost.localdomain>
Date: Fri, 29 Sep 2006 17:01:13 -0700
From: Matt Helsley <matthltc@...ibm.com>
To: Paul Jackson <pj@....com>
Cc: sekharan@...ibm.com, jtk@...ibm.com, jes@....com,
linux-kernel@...r.kernel.org, linux-audit@...hat.com,
viro@...iv.linux.org.uk, lse-tech@...ts.sourceforge.net,
sgrubb@...hat.com, hch@....de
Subject: Re: [Lse-tech] [RFC][PATCH 02/10] Task watchers v2 Benchmark
On Fri, 2006-09-29 at 13:13 -0700, Paul Jackson wrote:
> Matt wrote:
> > Heh, sorry about that. I do have some initial kernbench numbers.
>
> Thanks. You mention that one of the patches, Benchmark, reduced
> time spent in user space. I guess that means that patch hurt
> something ... though I'm confused ... wouldn't these patches risk
> spending more time in system space, not less in user space?
I would have thought so too, but it also appears to consistently reduce
time spent in the kernel. This seems to imply that the performance
improves for the first task watcher that gets added. I'd randomly guess
there's a branch misprediction when no watchers are registered.
My latest results will be more rigorous in that they show what a pure
2.6.18-mm1 run looks like. I've also removed the benchmark patch from
the series of runs. Unfortunately it takes approximately 24 hours to run
so it'll be a little while before I have the numbers.
> Do you have any analysis of the other runs? Just looking at raw
> numbers, when it's not a benchmark I've used recently, kinda fuzzes
> over my feeble brain.
Nope, sorry. I'll see what I can put together.
Cheers,
-Matt Helsley
-
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