From: Eric Piel <Eric.Piel@tremplin-utc.net>
To: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Dave Jones <davej@redhat.com>
Cc: CPUFreq Mailing List <cpufreq@lists.linux.org.uk>
Subject: Re: [PATCH] keep ignore_nice_load value when the ondemand govenor is reselected
Date: Thu, 23 Mar 2006 08:26:11 +0100 [thread overview]
Message-ID: <44224D93.5080101@tremplin-utc.net> (raw)
In-Reply-To: <4411485F.1010401@tremplin-utc.net>
10.03.2006 10:35, Eric Piel wrote/a écrit:
> Hello,
>
> With the ondemand governor, ignore_nice_load is reset each time the
> governor is selected. That's annoying because each time I change to
> another governor and change back to ondemand, I also have to set up
> ignore_nice_load. eg:
> # cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load
> 1
> # cpufreq-set -g powersave
> # cpufreq-set -g ondemand
> # cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load
> 0
>
> This behavior is also inconsistent with the other variables of
> /sys/devices/system/cpu/cpu0/cpufreq/ondemand/
>
> Attached is a patch that corrects the behavior.
Hello, I've sent this patch and "Warn if ondemand governor can not run
due to too long transition latency" mostly 2 weeks ago and didn't get
any feedback. It would be nice if at least this patch could make it to
2.6.17 as it fixes a glitch. Venki, could you ACK or NACK these patches?
Dave, if they don't apply cleanly against the cpufreq git tree (due to
the big clean up commit), I can redo them... just let me know :-)
Eric
next prev parent reply other threads:[~2006-03-23 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 9:35 [PATCH] keep ignore_nice_load value when the ondemand govenor is reselected Eric Piel
2006-03-23 7:26 ` Eric Piel [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 13:41 Pallipadi, Venkatesh
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=44224D93.5080101@tremplin-utc.net \
--to=eric.piel@tremplin-utc.net \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=venkatesh.pallipadi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox