From: Peter Zijlstra <peterz@infradead.org>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Fernando Luis Vazquez Cao <fernando_b1@lab.ntt.co.jp>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH 2/2] nohz: Synchronize sleep time stats with memory barriers
Date: Tue, 15 Apr 2014 13:14:10 +0200 [thread overview]
Message-ID: <20140415111410.GN13658@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140415105138.GO11096@twins.programming.kicks-ass.net>
On Tue, Apr 15, 2014 at 12:51:38PM +0200, Peter Zijlstra wrote:
> That said; I thing the fundamental flaw in the entire thing is
> accounting the entire nohz idle period as one type, since the period is
> basically unbounded.
So basically anything with the current per-cpu nr_iowait is bound to
yield crack induced results.
Like you said in your other email, we need to somehow intersect actual
idle time with the presence of iowait tasks. Now that's a global problem
and is unlikely to scale well. Which is of course why we have this
problem to begin with, if it were easy it'd be done right to begin with
(optimistic world view here).
next prev parent reply other threads:[~2014-04-15 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 20:17 [PATCH 1/2] nohz: Only update sleeptime stats locally Denys Vlasenko
2014-04-02 20:17 ` [PATCH 2/2] nohz: Synchronize sleep time stats with memory barriers Denys Vlasenko
2014-04-15 10:51 ` Peter Zijlstra
2014-04-15 11:14 ` Peter Zijlstra [this message]
2014-04-23 18:59 ` Denys Vlasenko
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=20140415111410.GN13658@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=dvlasenk@redhat.com \
--cc=fernando_b1@lab.ntt.co.jp \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=seto.hidetoshi@jp.fujitsu.com \
--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
all inboxes | Powered by JetHome®