From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: yangoliver <yang_oliver@hotmail.com>,
mingo@redhat.com, linux-kernel@vger.kernel.org,
Yong Yang <yangoliver@gmail.com>
Subject: Re: [PATCH 2/2] sched: Trace point sched_stat_sleep should cover iowait case
Date: Mon, 3 Aug 2015 20:43:38 +0200 [thread overview]
Message-ID: <20150803184338.GZ25159@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150803133528.11d77554@gandalf.local.home>
On Mon, Aug 03, 2015 at 01:35:28PM -0400, Steven Rostedt wrote:
> On Mon, 27 Jul 2015 09:11:52 -0400
> yangoliver <yang_oliver@hotmail.com> wrote:
>
> > Per sched_stat_sleep definition in sched.h, it should include
> > iowait case. This can also relect the design of sum_sleep_runtime
> > statistic, as this counter also includes the io_wait.
> >
> > Signed-off-by: Yong Yang <yangoliver@gmail.com>
> > ---
> > kernel/sched/fair.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> > index d113c3b..85677bf 100644
> > --- a/kernel/sched/fair.c
> > +++ b/kernel/sched/fair.c
> > @@ -3018,6 +3018,8 @@ static void enqueue_sleeper(struct cfs_rq *cfs_rq, struct sched_entity *se)
> > se->statistics.sum_sleep_runtime += delta;
> >
> > if (tsk) {
> > + trace_sched_stat_sleep(tsk, delta);
> > +
> > if (tsk->in_iowait) {
> > se->statistics.iowait_sum += delta;
> > se->statistics.iowait_count++;
>
No, that's broken in two ways. Firstly you don't change semantics of
stuff just because of a comment and secondly iowait has nothing what all
to do with INTERRUPTIBLE/sleep vs UNINTERRUPTIBLE/blocked.
And wtf are you doing sending sched patches and not Cc maintainers.
next prev parent reply other threads:[~2015-08-03 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1438002714-8158-1-git-send-email-yangoliver@gmail.com>
2015-07-27 13:11 ` yangoliver
2015-08-03 17:35 ` Steven Rostedt
2015-08-03 18:43 ` Peter Zijlstra [this message]
2015-08-04 6:47 ` Oliver Yang
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=20150803184338.GZ25159@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=yang_oliver@hotmail.com \
--cc=yangoliver@gmail.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
all inboxes | Powered by JetHome®