On 10/23/07, Jeff Dike <[EMAIL PROTECTED]> wrote:
>
> On Tue, Oct 23, 2007 at 04:21:03PM -0300, Hrishikesh wrote:
> >> Yes, that double negative was a slipup. I did get some numbers out and
> they
> >> look pretty good. I ran upto 5 instances of UML simultaneous
the
instances are simply idling. With NO_HZ applied, the change is minimal with
C3 residency still approximately 98%. UML is not even among the top three of
the bad-list of wakers-up :-)
Hrishikesh
On 10/18/07, Jeff Dike <[EMAIL PROTECTED]> wrote:
>
> On Wed, Oct 17, 2007 at 07:2
e put my
finger on where it is happening, but when CONFIG_NO_HZ is not enabled, the
timer_one_shot() is not being called at all. This means that the timer is
never set and hence returns 0 as old value whenever setitimer is called
later.
Hope that helps,
Hrishikesh
On 10/17/07, Jeff Dike <[EM
No, I think I haven't been clear enough. The story is right :-) When it is
"busy-looping" like in the second case is when the C3 residency comes down,
as expected. Like you said, it looks broken, and has to be fixed.
Regards,
Hrishikesh
On 10/17/07, Jeff Dike <[EMAIL PROTECTED]&
, 0}, {0, 0}) = 0
gettimeofday({1192648953, 437015}, NULL) = 0
setitimer(ITIMER_VIRTUAL, {it_interval={0, 0}, it_value={0, 0}},
{it_interval={0, 0}, it_value={0, 0}}) = 0
nanosleep({0, 0}, {0, 0}) = 0
Regards,
Hrishikesh
On 10/17/07, Jeff Dike <[EMAIL PROTECTED]>
do_nanosleep()). Yup this is a bad thing from the power consumption
viewpoint and you would like the processor to be in higher C-states most of
the time.
Regards,
Hrishikesh
On 10/17/07, Jeff Dike <[EMAIL PROTECTED]> wrote:
>
> On Tue, Oct 16, 2007 at 10:36:39PM -0400, Hrishikesh wro
does not happen when the tickless option _is_ enabled.
Regards,
Hrishikesh Amur
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration
