From: James Bruce <bruce@andrew.cmu.edu>
To: ambx1@neo.rr.com
Cc: "Theodore Ts'o" <tytso@mit.edu>, David Weinehall <tao@acc.umu.se>,
Lee Revell <rlrevell@joe-job.com>, Pavel Machek <pavel@ucw.cz>,
Marc Ballarin <Ballarin.Marc@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: Power consumption HZ100, HZ250, HZ1000: new numbers
Date: Wed, 03 Aug 2005 12:47:56 -0400 [thread overview]
Message-ID: <42F0F53C.5020403@andrew.cmu.edu> (raw)
In-Reply-To: <dbb91149e.1149edbb9@columbus.rr.com>
(Sorry all, but after receiving about 5 similar messages I'm going to
make one last reply.)
ambx1@neo.rr.com wrote:
> Also, my understanding was that when we properly support usb suspend,
> this won't be an issue anyway for much usb hardware. I think it's
> possible to put some mice to sleep when there isn't any motion and
> then wakeup later.
By the time we properly support USB suspend, it won't matter because the
dynamic tick patch will likely have been integrated. An argument for
why we should change a value in the future is pointless when the
question is what the value should be right now.
> 4.4% savings may not be much, but these things do add up.
A 300% increase in minimum sleep latency adds up quite quickly.
The point that people joining this thread keep missing is that we're
making a change that:
(a) offers a small benefit to laptop users
(b) messes up other uses such as video
(c) is likely to be completely obsolete by 2.6.14
> For a laptop's workload, I think this is worth it.
Good, so on your laptop go choose 100Hz. You already have to configure
your kernel to change values from their defaults anyway, otherwise you
won't see any of that 4.4% savings. However, please don't screw up
video and interactivity (1) for everyone who uses default values on
their desktops in order to get your savings.
(1) http://article.gmane.org/gmane.linux.kernel/319124/
Rather like the famous gcc 2.96, this is something that will confuse
users for some time to come. Just about every video app will need an
FAQ entry to say why 2.6.13 doesn't work as well and drops frames while
2.6.(x!=13) works just fine. Unless of course distros read this thread
and decide not to pick up this change; That I guess is the only reason
I'm still posting.
Now as Lee said, please let this thread die. We need to go work on
dyntick and test it on as much hardware as possible and try to uncover
any lurking bugs. If you care about saving power or multimedia, you
should test it too (think ~10% savings rather than 4.4%).
- Jim Bruce
next prev parent reply other threads:[~2005-08-03 16:49 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 15:20 Power consumption HZ100, HZ250, HZ1000: new numbers ambx1
2005-08-03 16:47 ` James Bruce [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-29 22:49 Marc Ballarin
2005-07-29 23:15 ` Lee Revell
2005-07-30 10:06 ` Marc Ballarin
2005-07-30 18:05 ` Lee Revell
2005-07-30 18:18 ` Zwane Mwaikambo
2005-07-30 18:14 ` Lee Revell
2005-07-30 18:35 ` Lee Revell
2005-08-01 20:00 ` Lee Revell
2005-07-30 19:51 ` Pavel Machek
2005-07-30 20:04 ` Lee Revell
2005-07-30 20:10 ` Pavel Machek
2005-07-31 20:21 ` James Bruce
2005-07-31 21:10 ` Pavel Machek
2005-07-31 21:41 ` Lee Revell
2005-07-31 21:57 ` James Bruce
2005-07-31 22:32 ` Pavel Machek
2005-07-31 23:20 ` Bernd Eckenfels
2005-08-01 1:59 ` Kyle Moffett
2005-08-02 9:08 ` Tomasz Torcz
2005-07-31 21:54 ` Lee Revell
2005-07-31 22:02 ` Lee Revell
2005-07-31 22:18 ` James Bruce
2005-07-31 22:07 ` Jim Crilly
2005-07-31 22:36 ` Pavel Machek
2005-07-31 22:39 ` Lee Revell
2005-08-01 3:49 ` Jim Crilly
2005-08-01 7:26 ` Pavel Machek
2005-08-01 18:16 ` Jim Crilly
2005-08-10 18:49 ` Bill Davidsen
2005-07-31 22:12 ` James Bruce
2005-07-31 22:47 ` Pavel Machek
2005-07-31 23:23 ` Lee Revell
2005-07-31 23:29 ` Pavel Machek
2005-07-31 23:53 ` Lee Revell
2005-08-01 7:28 ` Pavel Machek
2005-08-10 19:00 ` Bill Davidsen
2005-08-01 6:19 ` Stefan Seyfried
2005-08-01 16:07 ` Jan Knutar
2005-08-01 18:45 ` Lee Revell
2005-08-02 9:13 ` Tomasz Torcz
2005-08-02 14:58 ` Lee Revell
2005-08-01 7:44 ` David Weinehall
2005-08-01 16:18 ` James Bruce
2005-08-01 19:27 ` Lee Revell
2005-08-01 20:42 ` Theodore Ts'o
2005-08-02 4:50 ` James Bruce
2005-08-02 13:10 ` Stephen Clark
2005-08-02 14:02 ` Lee Revell
2005-08-02 14:12 ` Jens Axboe
2005-08-02 17:06 ` Folkert van Heusden
2005-08-02 17:45 ` linux-os (Dick Johnson)
2005-08-02 17:55 ` Lee Revell
2005-08-02 14:15 ` Con Kolivas
2005-08-02 14:20 ` Lars Marowsky-Bree
2005-08-02 14:22 ` Lee Revell
2005-08-02 15:18 ` Joel Jaeggli
2005-08-03 8:53 ` Oliver Neukum
2005-08-02 14:43 ` Jeff Garzik
2005-08-02 14:52 ` Lee Revell
2005-08-02 19:26 ` Lars Marowsky-Bree
2005-08-02 15:42 ` James Bruce
2005-08-02 15:58 ` Lee Revell
2005-08-02 17:02 ` Prakash Punnoor
2005-08-02 16:08 ` Ondrej Zary
2005-08-05 6:39 ` James Bruce
2005-08-11 19:22 ` Ondrej Zary
2005-08-03 9:19 ` Hans Kristian Rosbach
2005-08-03 13:57 ` Dmitry Torokhov
2005-08-04 12:52 ` Hans Kristian Rosbach
2005-08-02 6:45 ` Tony Lindgren
2005-08-02 11:23 ` Pavel Machek
2005-08-02 14:08 ` Lee Revell
2005-08-02 14:31 ` Roman Zippel
2005-08-02 11:25 ` Pavel Machek
2005-08-02 14:07 ` Lee Revell
2005-08-03 17:13 ` Stephen Ray
2005-08-03 19:12 ` Lee Revell
2005-07-30 20:08 ` Lee Revell
2005-07-30 10:06 ` Pavel Machek
2005-08-10 19:08 ` Bill Davidsen
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=42F0F53C.5020403@andrew.cmu.edu \
--to=bruce@andrew.cmu.edu \
--cc=Ballarin.Marc@gmx.de \
--cc=ambx1@neo.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rlrevell@joe-job.com \
--cc=tao@acc.umu.se \
--cc=tytso@mit.edu \
/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