From: Dominik Brodowski <linux@dominikbrodowski.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: cpufreq@lists.linux.org.uk, Alexander Clouter <alex@digriz.org.uk>
Subject: Re: [PATCH] cpufreq_(ondemand|conservative)
Date: Fri, 4 Feb 2005 21:39:08 +0100 [thread overview]
Message-ID: <20050204203908.GC8049@dominikbrodowski.de> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB6003E65CFF@scsmsx403.amr.corp.intel.com>
On Mon, Jan 31, 2005 at 03:40:24PM -0800, Pallipadi, Venkatesh wrote:
> >> > @@ -398,10 +455,10 @@
> >> >
> >> > j_dbs_info->prev_cpu_idle_up =
> >> > kstat_cpu(j).cpustat.idle +
> >> > - kstat_cpu(j).cpustat.iowait;
> >> > - j_dbs_info->prev_cpu_idle_down =
> >> > - kstat_cpu(j).cpustat.idle +
> >> > - kstat_cpu(j).cpustat.iowait;
> >> > + kstat_cpu(j).cpustat.iowait +
> >> > + kstat_cpu(j).cpustat.nice;
> >>
> >> Why are you adding cpustat.nice here unconditionally? You
> >don't do so in the
> >> sysfs write method, so I assume you should make this dependant on
> >> ignore_nice here as well.
> >>
> >Well by default 'ignore_nice = 0' so is there a need? Look in
> >the next hunk.
> >
>
> Probably it is better idea to have a if, even if the default is 0, as
> If we change the default in future, we don't have to look for all these
> dependent changes.
AFAICS we _do_ need it, as prev_cpu_idle_up is calculated
idle time +
iowait time +
(ignore_nice ? ignore time : NULL)
in many other places.
Dominik
next prev parent reply other threads:[~2005-02-04 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-31 23:40 [PATCH] cpufreq_(ondemand|conservative) Pallipadi, Venkatesh
2005-02-04 20:39 ` Dominik Brodowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-31 22:37 Pallipadi, Venkatesh
2005-02-01 9:02 ` Alexander Clouter
2005-01-23 15:00 Alexander Clouter
2005-01-29 20:00 ` Dominik Brodowski
2005-01-29 23:20 ` Alexander Clouter
2005-01-29 20:09 ` Dominik Brodowski
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=20050204203908.GC8049@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=alex@digriz.org.uk \
--cc=cpufreq@lists.linux.org.uk \
--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