From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Chase Douglas <chase.douglas@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
kernel-team <kernel-team@lists.ubuntu.com>
Subject: Re: [REGRESSION 2.6.30][PATCH 1/1] sched: defer idle accounting till after load update period
Date: Fri, 02 Apr 2010 09:59:44 +0200 [thread overview]
Message-ID: <1270195184.5109.523.camel@twins> (raw)
In-Reply-To: <alpine.LFD.2.00.1004012203270.32352@localhost.localdomain>
On Thu, 2010-04-01 at 22:18 +0200, Thomas Gleixner wrote:
> Well, the uninterruptible count imbalance is preventing us to calc the
> load avg per cpu, which is something the power saving folks are
> interested in.
>
> If that is fixed we probably have a good chance to collect the per cpu
> stuff and build a combined one - have not looked into the gory details
> of the math yet.
The problem with all this per-cpu loadavg is that it would require a
steady tick on each cpu to age this loadavg, which is quite in
contradiction with power savings as they rather like the nohz feature.
No idea yet on what to do about that.
next prev parent reply other threads:[~2010-04-02 8:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 13:41 [REGRESSION 2.6.30][PATCH 0/1] " Chase Douglas
2010-03-29 13:41 ` [REGRESSION 2.6.30][PATCH 1/1] " Chase Douglas
2010-03-29 14:41 ` Peter Zijlstra
2010-03-29 17:20 ` Chase Douglas
2010-04-01 19:27 ` Andrew Morton
2010-04-01 19:37 ` Thomas Gleixner
2010-04-01 20:00 ` Chase Douglas
2010-04-01 20:18 ` Thomas Gleixner
2010-04-01 20:32 ` Chase Douglas
2010-04-01 20:37 ` Thomas Gleixner
2010-04-02 7:59 ` Peter Zijlstra [this message]
2010-04-05 14:44 ` Chase Douglas
2010-04-01 19:56 ` Chase Douglas
2010-04-01 20:01 ` Thomas Gleixner
2010-04-13 20:39 ` Andrew Morton
2010-04-13 21:02 ` Thomas Gleixner
2010-04-13 21:06 ` Chase Douglas
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=1270195184.5109.523.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=chase.douglas@canonical.com \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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
Powered by JetHome