> The current idea is that we will have multiple governors changeable at run
> time only for
> DEBUG and DEVELOPMENT. On a standard end user system there will be one
> governor
> (current optimal governor) that will be loaded. This gives
> flexibality to experiments with governors and also
The current idea is that we will have multiple governors changeable at run
time only for
DEBUG and DEVELOPMENT. On a standard end user system there will be one
governor
(current optimal governor) that will be loaded. This gives
flexibality to experiments with governors and also easily have
IL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: Increased ipw2200 power usage with dynticks
>
>>
>> Nice to hear that cpuidle-menu governor gets 13.9W :-).
>> Powertop will need some changes to go with cpuidle, but that
>should be simple.
>>
>> We need some mor
Björn Steinbrink wrote:
On 2007.05.20 20:55:35 +0200, Andi Kleen wrote:
Björn Steinbrink <[EMAIL PROTECTED]> 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()
>
> Nice to hear that cpuidle-menu governor gets 13.9W :-).
> Powertop will need some changes to go with cpuidle, but that should be simple.
>
> We need some more testing for cpuidle before it gets into git.
> Len: Looks like cpuidle got dropped out of mm again. Can you merge it back it
>
Björn Steinbrink wrote:
On 2007.05.20 20:55:35 +0200, Andi Kleen wrote:
Björn Steinbrink [EMAIL PROTECTED] 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()
]
Subject: Re: Increased ipw2200 power usage with dynticks
Nice to hear that cpuidle-menu governor gets 13.9W :-).
Powertop will need some changes to go with cpuidle, but that
should be simple.
We need some more testing for cpuidle before it gets into git.
Len: Looks like cpuidle got dropped
Nice to hear that cpuidle-menu governor gets 13.9W :-).
Powertop will need some changes to go with cpuidle, but that should be simple.
We need some more testing for cpuidle before it gets into git.
Len: Looks like cpuidle got dropped out of mm again. Can you merge it back it
please.
It
OTECTED]
>Subject: Re: Increased ipw2200 power usage with dynticks
>
>On 2007.05.20 20:55:35 +0200, Andi Kleen wrote:
>> Björn Steinbrink <[EMAIL PROTECTED]> writes:
>> >
>> > Ok, it seems that ipw2200 is just a trigger for the
>problem here. AFAICT
>> >
On 2007.05.20 20:55:35 +0200, Andi Kleen wrote:
> Björn Steinbrink <[EMAIL PROTECTED]> 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
On 2007.05.20 20:55:35 +0200, Andi Kleen wrote:
Björn Steinbrink [EMAIL PROTECTED] 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?
ipw2200 power usage with dynticks
On 2007.05.20 20:55:35 +0200, Andi Kleen wrote:
Björn Steinbrink [EMAIL PROTECTED] 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
Björn Steinbrink <[EMAIL PROTECTED]> 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
Björn Steinbrink [EMAIL PROTECTED] 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.
On 2007.05.18 17:46:29 +0200, Björn Steinbrink wrote:
> Hi,
>
> while playing around with powertop, I noticed that my power usage wasn't
> what it used to be. In total idle mode, everything was fine, but as soon
> as I loaded the ipw2200 module and bring up the device, power usage
> rises to
On 2007.05.18 17:46:29 +0200, Björn Steinbrink wrote:
Hi,
while playing around with powertop, I noticed that my power usage wasn't
what it used to be. In total idle mode, everything was fine, but as soon
as I loaded the ipw2200 module and bring up the device, power usage
rises to about
Hi,
while playing around with powertop, I noticed that my power usage wasn't
what it used to be. In total idle mode, everything was fine, but as soon
as I loaded the ipw2200 module and bring up the device, power usage
rises to about 16.8W, while kernel up to 2.6.20 used only about 15.3W. A
day
Hi,
while playing around with powertop, I noticed that my power usage wasn't
what it used to be. In total idle mode, everything was fine, but as soon
as I loaded the ipw2200 module and bring up the device, power usage
rises to about 16.8W, while kernel up to 2.6.20 used only about 15.3W. A
day
18 matches
Mail list logo
