From: Yong Zhang <yong.zhang0@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Hillf Danton <dhillf@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Mike Galbraith <efault@gmx.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] sched: remove resetting exec_start in put_prev_task_rt()
Date: Fri, 10 Jun 2011 10:38:44 +0800 [thread overview]
Message-ID: <BANLkTi=Y+0h9bMaT6Z4+MhHf==POMKJNoQ@mail.gmail.com> (raw)
In-Reply-To: <1307622863.9218.40.camel@gandalf.stny.rr.com>
On Thu, Jun 9, 2011 at 8:34 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> I disagree. Yes the exec_start is reset there, but I like the fact that
> it's 0 when not running.
Actually this depends on how we look at the code:
if we set exec_start to 0 explicitly, as you said the code is more direct and
readable.
if we don't set exec_start to 0, we can save one instruction though
it's minor.
I have no strong opinion on either of them :)
BTW, put_prev_task_fair() doesn't set exec_start to 0.
Thanks,
Yong
--
Only stand for myself
next prev parent reply other threads:[~2011-06-10 2:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 14:03 [PATCH] sched: remove resetting exec_start in put_prev_task_rt() Hillf Danton
2011-06-01 14:22 ` Steven Rostedt
2011-06-02 8:04 ` Yong Zhang
2011-06-04 4:26 ` Hillf Danton
2011-06-09 12:34 ` Steven Rostedt
2011-06-10 2:38 ` Yong Zhang [this message]
2011-06-10 2:41 ` Steven Rostedt
2011-06-10 10:19 ` Peter Zijlstra
2011-06-10 14:48 ` Hillf Danton
2011-06-10 14:58 ` Steven Rostedt
2011-06-10 15:12 ` Hillf Danton
2011-08-14 16:03 ` [tip:sched/core] sched: Remove " tip-bot for Hillf Danton
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='BANLkTi=Y+0h9bMaT6Z4+MhHf==POMKJNoQ@mail.gmail.com' \
--to=yong.zhang0@gmail.com \
--cc=dhillf@gmail.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).