public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Pavel Machek <pavel@ucw.cz>
Cc: Con Kolivas <kernel@kolivas.org>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Dominik Brodowski <linux@dominikbrodowski.net>,
	Daniel Petrini <d.pensator@gmail.com>,
	Tony Lindgren <tony@atomide.com>,
	vatsa@in.ibm.com, ck list <ck@vds.kolivas.org>,
	Adam Belay <abelay@novell.com>,
	Zwane Mwaikambo <zwane@arm.linux.org.uk>
Subject: Re: [PATCH] i386 No Idle HZ aka dynticks 051221
Date: Mon, 26 Dec 2005 17:52:48 -0500	[thread overview]
Message-ID: <20051226225246.GA9915@thunk.org> (raw)
In-Reply-To: <20051226203806.GC1974@elf.ucw.cz>

On Mon, Dec 26, 2005 at 09:38:06PM +0100, Pavel Machek wrote:
> Stupid IBM. I've seen it appearing/disappearing, but did not work out
> when.
> 
> No-C4-on-AC is bad -- if you just disconnect AC and walk away, you are
> running without benefits of C4. Bad. Changing benchmarks depending on
> you booting on AC or battery also look nasty.

The moment you disconnect AC, it C4 automagically appears.  When you
reconnect to the AC mains, the C4 state disappears again, at least
from the listing displayed by /proc/acpi/processor/CPU0/power.  So the
first issue you brought up isn't a problem.

The fact that it could change the benchmarks results depending on
whether or you're running on battery or not is unfortunate, but in the
real world does it matter?   

More of an issue is that there are times when the laptop might think
that it's running of the AC mains, but in fact the owner may have
connected an external battery, and might _want_ the system to be as
frugal as possible with the power.

> > If dyntick is enabled, the laptop enters C4 state, which presumably is
> > a deeper, more power saving state, and it appears power saving effects
> > of dyntick is getting balanced off against the fact that C4 is never
> > getting entered when it is enabled.
> 
> Can you boot on AC power, then go to battery power to verify this theory?

Yep.  As I said, at least on my laptop, this is what
/proc/acpi/processor/CPU/power looks like when I am running on the AC
mains:

active state:            C2
max_cstate:              C8
bus master activity:     e7d24db4
states:
    C1:                  type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] time[00000000000000000000]
   *C2:                  type[C2] promotion[C3] demotion[C1] latency[001] usage[00084296] time[00000000000306642441]
    C3:                  type[C3] promotion[--] demotion[C2] latency[085] usage[00000000] time[00000000000000000000]

... and this is what it looks like when I am on battery:

active state:            C2
max_cstate:              C8
bus master activity:     6ef5bbbd
states:
    C1:                  type[C1] promotion[C2] demotion[--] latency[001] usage[00000010] time[00000000000000000000]
   *C2:                  type[C2] promotion[C3] demotion[C1] latency[001] usage[00001162] time[00000000000004425803]
    C3:                  type[C3] promotion[C4] demotion[C2] latency[085] usage[00000000] time[00000000000000000000]
    C4:                  type[C3] promotion[--] demotion[C3] latency[185] usage[00000000] time[00000000000000000000]

Whether I boot from AC power battery seems to be immaterial; what
seems to matter is whether or not the laptop is running on battery at
the moment that /proc/acpi/processor/CPU0/power is sampled.

						- Ted

  reply	other threads:[~2005-12-26 22:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-20 16:10 [PATCH] i386 No Idle HZ aka dynticks 051221 Con Kolivas
2005-12-20 17:27 ` Jan De Luyck
2005-12-20 19:39   ` Daniel Petrini
2005-12-20 20:46     ` Jan De Luyck
2005-12-25 17:16 ` Theodore Ts'o
2005-12-26  2:55   ` Theodore Ts'o
2005-12-26 18:47     ` Matthew Garrett
2005-12-26 18:56     ` Theodore Ts'o
2005-12-26 20:03     ` Dominik Brodowski
2005-12-26 20:38     ` Pavel Machek
2005-12-26 22:52       ` Theodore Ts'o [this message]
2005-12-26 23:27         ` Pavel Machek
2005-12-27 14:03           ` Pavel Machek
2005-12-27 14:22             ` C4 strangeness [was Re: [PATCH] i386 No Idle HZ aka dynticks 051221] Pavel Machek
2005-12-27 15:33               ` C4 non-strangeness [was: " Dominik Brodowski
2005-12-27 16:13                 ` Pavel Machek
2005-12-26 22:19     ` [PATCH] i386 No Idle HZ aka dynticks 051221 Dominik Brodowski
2005-12-27  0:33       ` Theodore Ts'o

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=20051226225246.GA9915@thunk.org \
    --to=tytso@mit.edu \
    --cc=abelay@novell.com \
    --cc=ck@vds.kolivas.org \
    --cc=d.pensator@gmail.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=pavel@ucw.cz \
    --cc=tony@atomide.com \
    --cc=vatsa@in.ibm.com \
    --cc=zwane@arm.linux.org.uk \
    /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