public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	Zachary Amsden <zach@vmware.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 0/11] VMI / Paravirt bugfixes for 2.6.21
Date: 6 Feb 2007 19:16:41 +0100
Date: Tue, 6 Feb 2007 19:16:41 +0100	[thread overview]
Message-ID: <20070206181641.GA35903@muc.de> (raw)
In-Reply-To: <1170765952.7324.15.camel@laptopd505.fenrus.org>

On Tue, Feb 06, 2007 at 01:45:52PM +0100, Arjan van de Ven wrote:
> On Tue, 2007-02-06 at 13:25 +0100, Andi Kleen wrote:
> > > hmm stolen time could even be useful without virtualization; to a large
> > > degree, if cpufreq reduces the speed of your cpu you have "stolen
> > > cycles" that way... I wonder if this concept can be used for that as
> > > well...
> 
> > 
> > I don't see the point, frankly.
> 
> I mean for showing the sysadmin that his system has spare capacity left.
> 
> right now top shows 50% in use (at say 600Mhz) while the 2.8Ghz
> processor obviously isn't even nearly half loaded.

Not necessarily.

You have no guarantee that it will go much faster at full frequency.
e.g. if the workload is memory bound then core frequency won't affect it
much.

Also if you're using automatic frequency scaling (which probably
the far majority of users do) then if anything keeps the system
busy for some time it will scale up anyways. This means even at 50%
load you will be likely running at full speed already.

I suspect there will be that many variables that automatic adjustment
is probably not useful.

-Andi

  reply	other threads:[~2007-02-06 18:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-06  3:52 [PATCH 0/11] VMI / Paravirt bugfixes for 2.6.21 Zachary Amsden
2007-02-06  4:27 ` Rusty Russell
2007-02-06  4:54   ` Zachary Amsden
2007-02-06  5:11     ` Rusty Russell
2007-02-06  5:24       ` Stephen Rothwell
2007-02-06  9:07       ` Arjan van de Ven
2007-02-06  9:25         ` Zachary Amsden
2007-02-06 12:25         ` Andi Kleen
2007-02-06 12:45           ` Arjan van de Ven
2007-02-06 18:16             ` Andi Kleen [this message]
2007-02-13 22:39           ` Rik van Riel

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=20070206181641.GA35903@muc.de \
    --to=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=chrisw@sous-sol.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=zach@vmware.com \
    /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