public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Kristian Rosbach <hk@isphuset.no>
To: linux-kernel@vger.kernel.org
Subject: Re: SMP cpu deep sleep
Date: Fri, 20 Aug 2004 11:42:13 +0200	[thread overview]
Message-ID: <1092994933.18271.21.camel@linux.local> (raw)
In-Reply-To: <200408200458.38591.jeffpc@optonline.net>

On Fri, 2004-08-20 at 10:58, Jeff Sipek wrote:
> On Friday 20 August 2004 04:06, Hans Kristian Rosbach wrote:
> > While reading through hotplug and speedstep patches
> > I came to think of a feature I think might be useful.
> >
> > In an SMP system there are several cpus, this generates
> > extra heat and power consuption even on idle load.
> > Is there a way to put all cpus but cpu1 into a kind of
> > deep sleep? Cpu1 would have to do all work (including irqs)
> > of course.
> 
> With Rusty's Hotplug CPU, a userspace script should be able to do this
by 
> cat'ing 1 or 0 into the appropriate sysfs file.

Nice, this can be done on non-hotplug motherboards as well?
How much time does it take to take the cpu up again?

It would need to be awakened whenever the activity increases
again, and that delay should not be too long.

Also, what effect does this have on cpu power consumtion
and thermal output? Does it lower it below normal idle?

-HK


  reply	other threads:[~2004-08-20  9:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20  8:06 SMP cpu deep sleep Hans Kristian Rosbach
2004-08-20  8:58 ` Jeff Sipek
2004-08-20  9:42   ` Hans Kristian Rosbach [this message]
2004-08-20 14:38     ` Zwane Mwaikambo
2004-08-20 16:44 ` Wes Felter
2004-08-21  0:53   ` Benjamin Herrenschmidt
2004-08-23 21:30   ` Bill Davidsen
2004-08-28 19:15     ` Alan Cox
2004-08-24 22:48   ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-08-20 14:30 Nakajima, Jun

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=1092994933.18271.21.camel@linux.local \
    --to=hk@isphuset.no \
    --cc=linux-kernel@vger.kernel.org \
    /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