From: Juri Lelli <juri.lelli@arm.com>
To: Wanpeng Li <wanpeng.li@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched/deadline: don't need to check throttled status when switched to dl
Date: Thu, 05 Mar 2015 09:24:05 +0000 [thread overview]
Message-ID: <54F820B5.7030503@arm.com> (raw)
In-Reply-To: <20150305013812.GA2966@kernel>
On 05/03/15 01:38, Wanpeng Li wrote:
> Ping Juri,
Yeah, I looked at it this morning. Looks good, thanks!
> On Thu, Feb 26, 2015 at 12:11:04PM +0800, Wanpeng Li wrote:
>> After commit 40767b0dc768 ("sched/deadline: Fix deadline parameter
>> modification handling"), deadline task throttled status is cleared
>> each time switch from dl, so throttled status always unset when
>> switch back, there is no need to check throttled status, this patch
>> drop the check.
>>
>> Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com>
Acked-by: Juri Lelli <juri.lelli@arm.com>
>> ---
>> kernel/sched/deadline.c | 8 --------
>> 1 file changed, 8 deletions(-)
>>
>> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
>> index ca391c0..cfb8fa7 100644
>> --- a/kernel/sched/deadline.c
>> +++ b/kernel/sched/deadline.c
>> @@ -1697,14 +1697,6 @@ static void switched_to_dl(struct rq *rq, struct task_struct *p)
>> {
>> int check_resched = 1;
>>
>> - /*
>> - * If p is throttled, don't consider the possibility
>> - * of preempting rq->curr, the check will be done right
>> - * after its runtime will get replenished.
>> - */
>> - if (unlikely(p->dl.dl_throttled))
>> - return;
>> -
>> if (task_on_rq_queued(p) && rq->curr != p) {
>> #ifdef CONFIG_SMP
>> if (p->nr_cpus_allowed > 1 && rq->dl.overloaded &&
>> --
>> 1.9.1
>
next prev parent reply other threads:[~2015-03-05 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 4:11 [PATCH] sched/deadline: don't need to check throttled status when switched to dl Wanpeng Li
2015-03-05 1:38 ` Wanpeng Li
2015-03-05 9:24 ` Juri Lelli [this message]
2015-03-05 9:18 ` Wanpeng Li
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=54F820B5.7030503@arm.com \
--to=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=wanpeng.li@linux.intel.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