All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: tglx@linutronix.de, mingo@elte.hu, yi.zhu@intel.com,
	linux-kernel@vger.kernel.org, arjan@infradead.org,
	venkatesh.pallipadi@intel.com, trenn@suse.de
Subject: Re: Increased ipw2200 power usage with dynticks
Date: 20 May 2007 20:55:35 +0200	[thread overview]
Message-ID: <p733b1re34o.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070519171011.GA1995@atjola.homenet>

Björn Steinbrink <B.Steinbrink@gmx.de> writes:
> 
> Ok, it seems that ipw2200 is just a trigger for the problem here. AFAICT
> the cause of the worse C state usage is that after ipw2200 has woken the
> cpu, acpi_processor_idle() chooses C2 (due to dma? bm? I have no
> idea...) as the prefered sleep state. Now without NO_HZ or when I hold
> down a key, there are interrupts that wake up the CPU and when
> acpi_processor_idle() is called again the promotion to C3/C4 happens.
> But with NO_HZ, there are no such interrupts, most wakeups are caused by
> ipw2200 and so the processor doesn't go any deeper than C2 most of the
> time and thus wastes lots of power.

The cpuidle governour code Venki is working on is supposed to address this.
There have been also earlier prototype patches by Adam Belay and
Thomas Renninger.

-Andi

  reply	other threads:[~2007-05-20 17:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 15:46 Increased ipw2200 power usage with dynticks Björn Steinbrink
2007-05-19 17:10 ` Björn Steinbrink
2007-05-20 18:55   ` Andi Kleen [this message]
2007-05-21  7:49     ` Björn Steinbrink
2007-05-21 17:24       ` Pallipadi, Venkatesh
2007-05-22  9:23         ` Andi Kleen
2007-05-22 18:00           ` Pallipadi, Venkatesh
2007-05-23 12:15             ` Andi Kleen
2007-05-22 17:43       ` 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=p733b1re34o.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=B.Steinbrink@gmx.de \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=trenn@suse.de \
    --cc=venkatesh.pallipadi@intel.com \
    --cc=yi.zhu@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.