public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: timothy.covell@ashavan.org
Cc: Rik van Riel <riel@conectiva.com.br>,
	Linus Torvalds <torvalds@transmeta.com>,
	Benjamin LaHaise <bcrl@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Davide Libenzi <davidel@xmailserver.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Scheduler, Can we save some juice ...
Date: 20 Dec 2001 01:52:47 -0500	[thread overview]
Message-ID: <1008831171.806.14.camel@phantasy> (raw)
In-Reply-To: <200112200637.fBK6b2Sr014173@svr3.applink.net>
In-Reply-To: <Pine.LNX.4.33L.0112200149330.15741-100000@imladris.surriel.com>  <200112200637.fBK6b2Sr014173@svr3.applink.net>

On Thu, 2001-12-20 at 01:33, Timothy Covell wrote:

> OK, here's another 0.1% for you.  Considering how Linux SMP
> doesn't have high CPU affinity, would it be possible to make a
> patch such that the additional CPUs remain in deep sleep/HALT
> mode until the first CPU hits a high-water mark of say 90% 
> utilization?  I've started doing this by hand with the (x)pulse
> application.   My goal is to save electricity and cut down on 
> excess heat when I'm just browsing the web and not compiling
> or seti@home'ing.

You'd probably be better off working against load and not CPU usage,
since a single app can hit you at 100% CPU.  Load average is the sort of
metric you want, since if there is more than 1 task waiting to run on
average, you will benefit from multiple CPUs.

That said, this would be easy to do in user space using the hotplug CPU
patch.  Monitor load average (just like any X applet does) and when it
crosses over the threshold: "echo 1 > /proc/sys/cpu/2/online"

Another solution would be to use CPU affinity to lock init (and thus all
tasks) to 0x00000001 or whatever and then start allowing 0x00000002 or
whatever when load gets too high.

My point: it is awful easy in user space.

	Robert Love


  parent reply	other threads:[~2001-12-20  6:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.33.0112181508001.3410-100000@penguin.transmeta.com>
2001-12-20  3:50 ` Scheduler ( was: Just a second ) Rik van Riel
2001-12-20  4:04   ` Ryan Cumming
2001-12-20  5:39   ` David S. Miller
2001-12-20  5:58     ` Linus Torvalds
2001-12-20  6:01       ` David S. Miller
2001-12-20 22:40         ` Troels Walsted Hansen
2001-12-20 23:55           ` Chris Ricker
2001-12-20 23:59             ` CaT
2001-12-21  0:06             ` Davide Libenzi
2001-12-20 11:29     ` Rik van Riel
2001-12-20 11:34       ` David S. Miller
2001-12-20  5:52   ` Linus Torvalds
2001-12-20  6:33   ` Scheduler, Can we save some juice Timothy Covell
2001-12-20  6:50     ` Ryan Cumming
2001-12-20  6:52     ` Robert Love [this message]
2001-12-20 17:39       ` Timothy Covell

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=1008831171.806.14.camel@phantasy \
    --to=rml@tech9.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bcrl@redhat.com \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=timothy.covell@ashavan.org \
    --cc=torvalds@transmeta.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