From: Oleg Nesterov <oleg@redhat.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Jaromir Capik <jcapik@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ania Honess <ahoness@redhat.com>,
atomlin@redhat.com, asolanas@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: proc/stat: idle goes backward
Date: Fri, 16 Aug 2013 17:13:39 +0200 [thread overview]
Message-ID: <20130816151339.GA29675@redhat.com> (raw)
In-Reply-To: <20130816150122.GB24210@somewhere>
On 08/16, Frederic Weisbecker wrote:
>
> On Fri, Aug 16, 2013 at 04:47:04PM +0200, Oleg Nesterov wrote:
> >
> > Questions:
> >
> > - Any other reason why it can be non-monotonic?
> >
> > - Should we fix this or should we document that userspace
> > should handle this itself?
> >
> > IOW, is this is bug or not?
>
> I don't know if we want to fix it (I personally think we should because it is not the
> first time I hear complains about this) but if we do, here is a possible fix:
>
> https://lkml.org/lkml/2013/8/8/638
Thanks! it is not easy to read the patches on lkml.org and I do
not understand this code enough. But it seems that this should
address my concerns, including the "even ignoring drivers/cpuidle/".
Except, I am not sure that these changes handle the case when
nr_iowait() change in between.
Are you going to resend?
Oleg.
next prev parent reply other threads:[~2013-08-16 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v5wUE000000000000000000000000000000000000000000000MRITO500uRRuI-89T-iqXCkOVGWF4w@sfdc.net>
[not found] ` <1904614521.2884383.1376487067689.JavaMail.root@redhat.com>
[not found] ` <1277145964.2082352.1376490809716.JavaMail.root@redhat.com>
2013-08-16 14:47 ` proc/stat: idle goes backward Oleg Nesterov
2013-08-16 15:01 ` Frederic Weisbecker
2013-08-16 15:13 ` Oleg Nesterov [this message]
2013-08-16 15:30 ` Frederic Weisbecker
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=20130816151339.GA29675@redhat.com \
--to=oleg@redhat.com \
--cc=ahoness@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=asolanas@redhat.com \
--cc=atomlin@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jcapik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mingo@kernel.org \
--cc=schwidefsky@de.ibm.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