From: Wanpeng Li <wanpeng.li@linux.intel.com>
To: Kirill Tkhai <ktkhai@parallels.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@arm.com>,
juri.lelli@gmail.com, linux-kernel@vger.kernel.org,
Wanpeng Li <wanpeng.li@linux.intel.com>
Subject: Re: [PATCH v2 1/6] sched/rt: check if curr can be pushed/pulled somewhere else in advance
Date: Fri, 31 Oct 2014 05:59:15 +0800 [thread overview]
Message-ID: <20141030215915.GA7478@kernel> (raw)
In-Reply-To: <1414681265.8574.83.camel@tkhai>
Hi Kirill,
On Thu, Oct 30, 2014 at 06:01:05PM +0300, Kirill Tkhai wrote:
>Hi,
>
>В Чт, 30/10/2014 в 22:16 +0800, Wanpeng Li пишет:
>> This patch checks if current can be pushed/pulled somewhere else
>> in advance to make logic clear, the same behavior as rt class.
>>
>> - If current can't be migrated, useless to reschedule, let's hope
>> task can move out.
>> - If task is migratable, so let's not schedule it and see if it
>> can be pushed or pulled somewhere else.
>
>No functional changes, are they? So I'd suggest to change subject
>on something connected with "cleanup".
>
>Also, the description confuses. Please, write that code was cleaned
>up, and that comments were added.
>
Ok.
>> Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com>
>> ---
>> kernel/sched/rt.c | 14 ++++++++++----
>> 1 file changed, 10 insertions(+), 4 deletions(-)
>>
>> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
>> index d024e6c..a0b51aa 100644
>> --- a/kernel/sched/rt.c
>> +++ b/kernel/sched/rt.c
>> @@ -1351,16 +1351,22 @@ out:
>>
>> static void check_preempt_equal_prio(struct rq *rq, struct task_struct *p)
>> {
>> - if (rq->curr->nr_cpus_allowed == 1)
>> + /*
>> + * Current can't be migrated, useless to reschedule,
>> + * let's hope p can move out.
>> + */
>> + if (rq->curr->nr_cpus_allowed == 1 ||
>> + !cpupri_find(&rq->rd->cpupri, rq->curr, NULL))
>> return;
>
>All conditions of multi-line if() should be aligned the same:
>
>+ if (rq->curr->nr_cpus_allowed == 1 ||
>+ !cpupri_find(&rq->rd->cpupri, rq->curr, NULL))
>
I will update the patch in next version, thanks for your review.
Regards,
Wanpeng Li
>>
>> + /*
>> + * p is migratable, so let's not schedule it and
>> + * see if it is pushed or pulled somewhere else.
>> + */
>> if (p->nr_cpus_allowed != 1
>> && cpupri_find(&rq->rd->cpupri, p, NULL))
>> return;
>>
>> - if (!cpupri_find(&rq->rd->cpupri, rq->curr, NULL))
>> - return;
>> -
>> /*
>> * There appears to be other cpus that can accept
>> * current and none to run 'p', so lets reschedule
>
>Thanks,
>Kirill
>
prev parent reply other threads:[~2014-10-30 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 14:16 [PATCH v2 1/6] sched/rt: check if curr can be pushed/pulled somewhere else in advance Wanpeng Li
2014-10-30 14:16 ` [PATCH v2 2/6] sched/deadline: fix artificial overrun introduced by yield_task_dl Wanpeng Li
2014-10-30 14:17 ` [PATCH v2 3/6] sched/dl: add deadline rq status print Wanpeng Li
2014-10-30 14:17 ` [PATCH v2 4/6] sched/dl: push task away if the deadline is equal to curr during wakeup Wanpeng Li
2014-10-30 14:17 ` [PATCH v2 5/6] sched/deadline: reschedule from switched_from_dl() after a successful pull Wanpeng Li
2014-10-30 14:17 ` [PATCH v2 6/6] sched/dl: don't check CONFIG_SMP in switched_from_dl Wanpeng Li
2014-10-30 15:01 ` [PATCH v2 1/6] sched/rt: check if curr can be pushed/pulled somewhere else in advance Kirill Tkhai
2014-10-30 21:59 ` Wanpeng Li [this message]
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=20141030215915.GA7478@kernel \
--to=wanpeng.li@linux.intel.com \
--cc=juri.lelli@arm.com \
--cc=juri.lelli@gmail.com \
--cc=ktkhai@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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