From: Peter Zijlstra <peterz@infradead.org>
To: joni@shade-fx.com
Cc: linux-kernel@vger.kernel.org, Dave Jones <davej@redhat.com>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>
Subject: Re: [PATCH] cpufreq: ondemand ignore_nice_level
Date: Tue, 09 Aug 2011 12:12:39 +0200 [thread overview]
Message-ID: <1312884759.22367.64.camel@twins> (raw)
In-Reply-To: <4e403bd4.5YAAoSWMDWtU5KOP%joni@shade-fx.com>
How very good of you to CC all the relevant maintainers..
On Mon, 2011-08-08 at 22:41 +0300, joni@shade-fx.com wrote:
> @@ -3755,7 +3755,7 @@ unsigned long long thread_group_sched_runtime(struct task_struct *p)
> * @cputime_scaled: cputime scaled by cpu frequency
> */
> void account_user_time(struct task_struct *p, cputime_t cputime,
> - cputime_t cputime_scaled)
> + cputime_t cputime_scaled)
> {
> struct cpu_usage_stat *cpustat = &kstat_this_cpu.cpustat;
> cputime64_t tmp;
I'm very sure the old alignment was preferred.
> @@ -3769,9 +3769,11 @@ void account_user_time(struct task_struct *p, cputime_t cputime,
> tmp = cputime_to_cputime64(cputime);
> if (TASK_NICE(p) > 0)
> cpustat->nice = cputime64_add(cpustat->nice, tmp);
> - else
> + else
> cpustat->user = cputime64_add(cpustat->user, tmp);
>
> + cpustat->nicevalue[TASK_USER_PRIO(p)] = cputime64_add(cpustat->nicevalue[TASK_USER_PRIO(p)], tmp);
> +
> cpuacct_update_stats(p, CPUACCT_STAT_USER, cputime);
> /* Account for user time used */
> acct_update_integrals(p);
Yay! more senseless accounting.. we really need more of that. What's
even better is your data array being 320 bytes spanning 5 cachelines,
and thus the above almost guarantees a cacheline miss.
All round good stuff, and as DaveJ already pointed out, all without any
justification what so ever.
next prev parent reply other threads:[~2011-08-09 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 19:41 [PATCH] cpufreq: ondemand ignore_nice_level joni
2011-08-08 21:10 ` Dave Jones
2011-08-09 10:12 ` Peter Zijlstra [this message]
2011-08-09 17:14 ` Joni Martikainen
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=1312884759.22367.64.camel@twins \
--to=peterz@infradead.org \
--cc=arjan.van.de.ven@intel.com \
--cc=davej@redhat.com \
--cc=joni@shade-fx.com \
--cc=linux-kernel@vger.kernel.org \
/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