From: Yong Zhang <yong.zhang0@gmail.com>
To: "Michael J. Wang" <mjwang@broadcom.com>
Cc: "mingo@elte.hu" <mingo@elte.hu>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>
Subject: Re: [PATCH 1/1] scheduler: minor improvement to pick_next_highest_task_rt in linux-3.3
Date: Wed, 21 Mar 2012 10:12:29 +0800 [thread overview]
Message-ID: <20120321021229.GB19766@zhy> (raw)
In-Reply-To: <2EF88150C0EF2C43A218742ED384C1BC0FC84327@IRVEXCHMB08.corp.ad.broadcom.com>
On Wed, Mar 21, 2012 at 01:56:47AM +0000, Michael J. Wang wrote:
> Ah, I see. Forgot about the length of my comment line.
>
> Should I reformat my patch and send it again?
It'll be better, and I think Peter/Ingo will happy with it.
Thanks,
Yong
>
> Thanks,
> Michael
>
>
> -----Original Message-----
> From: Yong Zhang [mailto:yong.zhang0@gmail.com]
> Sent: Tuesday, March 20, 2012 6:41 PM
> To: Michael J. Wang
> Cc: mingo@elte.hu; peterz@infradead.org; linux-kernel@vger.kernel.org; rostedt@goodmis.org
> Subject: Re: [PATCH 1/1] scheduler: minor improvement to pick_next_highest_task_rt in linux-3.3
>
> On Mon, Mar 19, 2012 at 10:26:19PM +0000, Michael J. Wang wrote:
> > From: Michael J Wang <mjwang@broadcom.com>
> >
> > Avoid extra work by continuing on to the next rt_rq if the highest prio task in current rt_rq is the same priority as our candidate task.
> >
> > Signed-off-by: Michael J Wang <mjwang@broadcom.com>
> >
> > ---
> >
> > More detailed explanation: if next is not NULL, then we have found a candidate task, and its priority is next->prio. Now we are looking for an even higher priority task in the other rt_rq's. idx is the highest priority in the current candidate rt_rq. In the current 3.3 code, if idx is equal to next->prio, we would start scanning the tasks in that rt_rq and replace the current candidate task with a task from that rt_rq. But the new task would only have a priority that is equal to our previous candidate task, so we have not advanced our goal of finding a higher prio task. So we should avoid the extra work by continuing on to the next rt_rq if idx is equal to next->prio.
> >
>
> You should limit characters of each line to 80 if possible.
>
> And before sending you patch, linux-source/scripts/checkpatch.pl maybe
> give you some clues whether there is some warning/error. If there are,
> fix them.
>
> Only for what your patch wants to show:
> Reviewed-by: Yong Zhang <yong.zhang0@gmail.com>
>
> Thanks,
> Yong
>
> > --- linux-3.3/kernel/sched/rt.c.orig 2012-03-18 16:15:34.000000000 -0700
> > +++ linux-3.3/kernel/sched/rt.c 2012-03-19 14:52:54.585391702 -0700
> > @@ -1403,7 +1403,7 @@ static struct task_struct *pick_next_hig
> > next_idx:
> > if (idx >= MAX_RT_PRIO)
> > continue;
> > - if (next && next->prio < idx)
> > + if (next && next->prio <= idx)
> > continue;
> > list_for_each_entry(rt_se, array->queue + idx, run_list) {
> > struct task_struct *p;
> >
> >
> >
> >
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> Only stand for myself
>
> N�����r��y���b�X��ǧv�^�){.n�+����{����zX��\x17��ܨ}���Ơz�&j:+v���\a����zZ+��+zf���h���~����i���z�\x1e�w���?����&�)ߢ^[f��^jǫy�m��@A�a��\x7f�\f0��h�\x0f�i\x7f
--
Only stand for myself
next prev parent reply other threads:[~2012-03-21 2:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 22:26 [PATCH 1/1] scheduler: minor improvement to pick_next_highest_task_rt in linux-3.3 Michael J. Wang
2012-03-20 13:59 ` Steven Rostedt
2012-03-21 1:40 ` Yong Zhang
2012-03-21 1:56 ` Michael J. Wang
2012-03-21 2:12 ` Yong Zhang [this message]
2012-03-21 7:49 ` Michael J. Wang
2012-03-21 9:06 ` Peter Zijlstra
2012-03-21 18:33 ` Michael J. Wang
2012-03-21 19:35 ` Peter Zijlstra
2012-03-22 7:50 ` Ingo Molnar
2012-03-27 15:35 ` [tip:sched/urgent] sched/rt: Improve pick_next_highest_task_rt() tip-bot for Michael J Wang
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=20120321021229.GB19766@zhy \
--to=yong.zhang0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjwang@broadcom.com \
--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