From: Jeff Dike <jdike@addtoit.com>
To: Hrishikesh <hrishikesh.amur@gmail.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Dramatic drop in C3 state residency with NO_HZ patches
Date: Wed, 17 Oct 2007 13:19:20 -0400 [thread overview]
Message-ID: <20071017171920.GA10388@c2.user-mode-linux.org> (raw)
In-Reply-To: <1f154f440710170916j4fdb857fw40c9b2fd2b66f63f@mail.gmail.com>
On Wed, Oct 17, 2007 at 12:16:18PM -0400, Hrishikesh wrote:
> This is when I patch the UML kernel with the NO_HZ patches that you put up
> last month.. on 2.6.23-rc6-mm1.
Hmmm, that's exactly the opposite of what I would expect. A idle
non-NO_HZ UML should be waking up 100 times/sec, while I see much
longer sleeps with an idle NO_HZ UML, up to 2-3 seconds.
Can you strace both cases and see how often the NO_HZ UML is waking up
compared to the non-NO_HZ one?
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
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/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2007-10-17 17:19 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 [this message]
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
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=20071017171920.GA10388@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=hrishikesh.amur@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.