linux-um archives
 help / color / mirror / Atom feed
From: Hrishikesh <hrishikesh.amur@gmail.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Dramatic drop in C3 state residency with NO_HZ patches
Date: Tue, 23 Oct 2007 19:53:01 -0400	[thread overview]
Message-ID: <1f154f440710231653s69d02dbepc552c5fe8d7f2b3f@mail.gmail.com> (raw)
In-Reply-To: <20071023213545.GA11026@c2.user-mode-linux.org>


[-- Attachment #1.1: Type: text/plain, Size: 1113 bytes --]

On 10/23/07, Jeff Dike <jdike@addtoit.com> 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 simultaneously and in
> the
> >> tickful case, each instance adds roughly about 100 wakeups per second.
>
> > HZ == 100, so that makes sense.


>> So
> >> after 5 instances, C3 residency comes down to about 95% when all 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 :-)
>
> > Cool.  I'm suprised that 500 wakeups/sec only brings you down < 5%.


Hmm,  powertop shows  500 wakeups  on  part of UML, but the actual number of
wakeups for the processor is much  lesser..  Guess there is  some  batching
that  is happening.

> So, things are good, except I need to figure out the !NO_HZ busy loop.
> >
> >                                Jeff
> >
> > --
> > Work email - jdike at linux dot intel dot com


Hrishi

[-- Attachment #1.2: Type: text/html, Size: 2019 bytes --]

[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 194 bytes --]

_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2007-10-23 23:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17  2:36 [uml-devel] Dramatic drop in C3 state residency with NO_HZ patches Hrishikesh
2007-10-17 15:55 ` Jeff Dike
2007-10-17 16:16   ` Hrishikesh
2007-10-17 17:19     ` Jeff Dike
2007-10-17 19:43       ` Hrishikesh
2007-10-17 20:45         ` Jeff Dike
2007-10-17 23:29           ` Hrishikesh
2007-10-18 20:04             ` Jeff Dike
2007-10-23 19:21               ` Hrishikesh
2007-10-23 21:35                 ` Jeff Dike
2007-10-23 23:53                   ` Hrishikesh [this message]
2007-10-18  8:06           ` Hrishikesh
2007-11-06 18:02         ` Jeff Dike

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1f154f440710231653s69d02dbepc552c5fe8d7f2b3f@mail.gmail.com \
    --to=hrishikesh.amur@gmail.com \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox