public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Oliver Neukum <oliver@neukum.org>,
	kernel list <linux-kernel@vger.kernel.org>,
	Linux-pm mailing list <linux-pm@lists.osdl.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [RFC] sleepy linux
Date: Wed, 26 Dec 2007 12:54:30 -0800	[thread overview]
Message-ID: <4772BF86.4010906@zytor.com> (raw)
In-Reply-To: <20071226205103.GG8094@elf.ucw.cz>

Pavel Machek wrote:
> On Wed 2007-12-26 12:43:56, H. Peter Anvin wrote:
>> Oliver Neukum wrote:
>>> Am Mittwoch, 26. Dezember 2007 19:56:59 schrieb H. Peter Anvin:
>>>>> 3) Network card that is either down
>>>>>    or can wake up system on any packet (and not loose too many packets)
>>>>>
>>>> This is the big crux I see.  You're going to constantly wake up the 
>>>> machine due to broadcast packets, and spend a lot of power just going in 
>>>> and out of S3.
>>> How many machines care a lot about saving power while they are connected
>>> to an ethernet? Wlan might be more of a problem.
>> A lot of them should.  An inordinate amount of machines sit there burning 
>> power for no reason.  You can argue that S3 isn't needed -- that nohz + 
>> C3/C4 + turning off the screen would be enough, and that might be
>> + legit.  
> 
> NOHZ + C4 + turn off screen + turn off disk + turn off SATA is still
> ~8W on thinkpad x60.
> 
> S3 is ~1W.
> 
> That's quite significant difference.
> 
> (But yes, connected-to-ethernet is not most important use scenario.)
> 								Pavel

Still... if we could get the desktops of the world down anywhere close 
to that range when not used, it would be a huge win.

	-hpa

  reply	other threads:[~2007-12-26 20:55 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-25 23:07 [RFC] sleepy linux Pavel Machek
2007-12-26 17:28 ` Oliver Neukum
2007-12-26 19:02   ` Pavel Machek
2007-12-26 20:17   ` Pavel Machek
2007-12-26 20:23     ` Oliver Neukum
2007-12-26 20:32       ` Pavel Machek
2007-12-26 23:15         ` Oliver Neukum
2007-12-29 23:48           ` Pavel Machek
2007-12-27  9:41         ` Oliver Neukum
2007-12-29 23:51           ` Pavel Machek
2007-12-30 16:39             ` Oliver Neukum
2007-12-31 14:44               ` Pavel Machek
2008-01-02 10:52                 ` Oliver Neukum
2007-12-26 18:56 ` H. Peter Anvin
2007-12-26 19:00   ` Pavel Machek
2007-12-26 19:22     ` H. Peter Anvin
2007-12-26 20:08   ` Oliver Neukum
2007-12-26 20:43     ` H. Peter Anvin
2007-12-26 20:51       ` Pavel Machek
2007-12-26 20:54         ` H. Peter Anvin [this message]
2007-12-29 23:44           ` Pavel Machek
2007-12-26 20:09 ` [linux-pm] " Igor Stoppa
2007-12-30 11:15 ` Ingo Molnar
2008-01-05 21:51   ` Pavel Machek
2008-01-08 16:37     ` Ingo Molnar
2008-01-08 19:15       ` Pavel Machek

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=4772BF86.4010906@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=oliver@neukum.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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