From: Joe Perches <joe@perches.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Todd Kjos <tkjos@google.com>, Joel Fernandes <joelaf@google.com>,
Colin Cross <ccross@android.com>,
Ramesh Thomas <ramesh.thomas@intel.com>,
Mel Gorman <mgorman@suse.de>, Ingo Molnar <mingo@redhat.com>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Alex Shi <alex.shi@linaro.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] cpuidle/drivers/menu: Remove get_loadavg in the performance multiplier
Date: Thu, 04 Oct 2018 10:16:46 -0700 [thread overview]
Message-ID: <dba47f670a8aab2ff68e664b3a138ca456fbfd74.camel@perches.com> (raw)
In-Reply-To: <4541426c-8c73-7fe6-b3b6-9707861564ce@linaro.org>
On Thu, 2018-10-04 at 10:40 +0200, Daniel Lezcano wrote:
> On 04/10/2018 10:22, Rafael J. Wysocki wrote:
> > On Thu, Oct 4, 2018 at 9:42 AM Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
> > > The function get_loadavg() returns almost always zero. To be more
> > > precise, statistically speaking for a total of 1023379 times passing
> > > in the function, the load is equal to zero 1020728 times, greater than
> > > 100, 610 times, the remaining is between 0 and 5.
[]
> > > diff --git a/drivers/cpuidle/governors/menu.c b/drivers/cpuidle/governors/menu.c
[]
> > > @@ -359,7 +346,8 @@ static int menu_select(struct cpuidle_driver *drv, struct cpuidle_device *dev,
> > > * Use the performance multiplier and the user-configurable
> > > * latency_req to determine the maximum exit latency.
> > > */
> > > - interactivity_req = data->predicted_us / performance_multiplier(nr_iowaiters, cpu_load);
> > > + interactivity_req = data->predicted_us /
> > > + performance_multiplier(nr_iowaiters);
> >
> > I wouldn't break this line.
>
> Ok, mind if I break the line in a separate patch before ? (my git
> pre-commit hook runs checkpatch and it complains and prevent to commit
> the patch because of the line length (94)).
A lot of this file uses > 80 column lines.
As well, the identifiers here are relatively long.
Long identifier lengths and 80 column lines are generally
incompatible.
I suggest you change your script to allow > 80 column lines
using the checkpatch command-line option --ignore==long_line
or perhaps add --max-line-length=<some higher value> or at
least allow some other senstible interactivity when the silly
script bleats some mindless warning or another.
next prev parent reply other threads:[~2018-10-04 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 7:42 [PATCH 1/2] sched: Factor out nr_iowait and nr_iowait_cpu Daniel Lezcano
2018-10-04 7:42 ` [PATCH 2/2] cpuidle/drivers/menu: Remove get_loadavg in the performance multiplier Daniel Lezcano
2018-10-04 7:57 ` Peter Zijlstra
2018-10-04 8:12 ` Daniel Lezcano
2018-10-04 9:35 ` Peter Zijlstra
2018-10-04 8:22 ` Rafael J. Wysocki
2018-10-04 8:40 ` Daniel Lezcano
2018-10-04 8:47 ` Rafael J. Wysocki
2018-10-04 9:36 ` Peter Zijlstra
2018-10-04 9:39 ` Rafael J. Wysocki
2018-10-04 17:16 ` Joe Perches [this message]
2018-10-04 7:46 ` [PATCH 1/2] sched: Factor out nr_iowait and nr_iowait_cpu Rafael J. Wysocki
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=dba47f670a8aab2ff68e664b3a138ca456fbfd74.camel@perches.com \
--to=joe@perches.com \
--cc=alex.shi@linaro.org \
--cc=ccross@android.com \
--cc=daniel.lezcano@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=joelaf@google.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pombredanne@nexb.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=ramesh.thomas@intel.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=tkjos@google.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