From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: Jordan Crouse <jordan.crouse-5C7GfCeVMHo@public.gmane.org>
Cc: Linux-pm mailing list <linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: comments on irc log
Date: Mon, 21 Mar 2005 21:03:16 +0100 [thread overview]
Message-ID: <20050321200316.GG1390@elf.ucw.cz> (raw)
In-Reply-To: <20050321130612.135d726e-aftB2sG12IhaqnLngUycEA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
Hi!
> > > 21:52:11< pavelm> I was playing with variable scheduling ticks here,
> > > hoping to save some power. 21:52:31< pavelm> How big power savings
> > > should I expect? 21:52:48< pavelm> What cpu will benefit most?
> > > 21:53:04< pavelm> Is there easy way to measure it?
> > >
> > > I played with that too on some PPCs and was surprised by the absence
> > > of benefit, but I might have done something wrong, I need to
> > > instrument the stuff better.
> >
> > Difference between HZ=100 and HZ=1000 was measuerd to be approx. as
> > big as disk spinnned up vs. spinned down (i.e. watt or so) by
> > seife.... Not *that* unimportant. But it took month or so to get that
> > data, because he was basically measuring runtime from full to empty
> > battery.
>
> Have any of these patches been published? I've been playing with
> variable ticks too, and I would like to see what other people have been
> doing (as so far, the only thing I've managed to do is commit crimes
> against nature and the idle loop).
Try searching lkml archives for CONFIG_NO_IDLE_HZ.... There are
actually two different codebases floating around.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-03-21 20:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 2:32 comments on irc log Benjamin Herrenschmidt
2005-03-18 16:56 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0503181147110.1099-100000-3WpdWqXrU/qjv4eRiOYp3g@public.gmane.org>
2005-03-18 18:14 ` Pavel Machek
2005-03-18 23:07 ` Benjamin Herrenschmidt
2005-03-18 23:18 ` Pavel Machek
[not found] ` <20050318231801.GE24449-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-19 1:21 ` Benjamin Herrenschmidt
2005-03-19 3:23 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0503182205040.30560-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2005-03-19 10:33 ` Pavel Machek
[not found] ` <20050319103351.GM24449-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-19 15:49 ` Alan Stern
2005-03-19 12:02 ` Benjamin Herrenschmidt
2005-03-19 10:32 ` Pavel Machek
2005-03-18 18:13 ` Pavel Machek
[not found] ` <20050318181317.GD18427-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-18 23:15 ` Benjamin Herrenschmidt
2005-03-21 20:06 ` Jordan Crouse
[not found] ` <20050321130612.135d726e-aftB2sG12IhaqnLngUycEA@public.gmane.org>
2005-03-21 20:03 ` Pavel Machek [this message]
2005-03-23 19:46 ` David Brownell
[not found] ` <200503231146.17105.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2005-03-23 19:53 ` David Brownell
[not found] ` <200503231153.48230.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2005-03-23 20:16 ` Todd Poynor
[not found] ` <4241CE9B.5050604-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
2005-03-23 20:46 ` David Brownell
[not found] ` <200503231246.05656.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2005-03-24 1:57 ` Todd Poynor
2005-03-23 21:08 ` Pavel Machek
[not found] ` <20050323210835.GF30704-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-23 21:33 ` David Brownell
[not found] ` <200503231333.22647.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2005-03-23 21:53 ` Pavel Machek
[not found] ` <20050323215330.GJ30704-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-24 18:40 ` Patrick Mochel
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=20050321200316.GG1390@elf.ucw.cz \
--to=pavel-alswssmvlrq@public.gmane.org \
--cc=jordan.crouse-5C7GfCeVMHo@public.gmane.org \
--cc=linux-pm-qjLDD68F18O7TbgM5vRIOg@public.gmane.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