linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 6/7] sched/deadline: depend on clearing throttled status in replenish_dl_entity
Date: Tue, 21 Apr 2015 09:16:47 +0100	[thread overview]
Message-ID: <5536076F.9020404@arm.com> (raw)
In-Reply-To: <1428310399-13489-6-git-send-email-wanpeng.li@linux.intel.com>

Hi,

On 06/04/2015 09:53, Wanpeng Li wrote:
> Since the natural place to clear ->dl_throttled is in replenish_dl_entity(), and 
> the task which is adjusted the priority is the current, it will be dequeued and 
> then enqueued w/ replenish which can guarantee ->dl_throttled can be cleared, 
> this patch drop the clear throttled status in function rt_mutex_setprio.
> 

Patch looks good. But, I'd slightly change subject and changelog. Something like
this, maybe?

sched/core: remove superfluous resetting of dl_throttled flag

Resetting dl_throttled flag in rt_mutex_setprio (for a task that is going
to be boosted) is superfluous, as the natural place to do so is in
replenish_dl_entity(). If the task was on the runqueue and it is boosted
by a DL task, it will be enqueued back with ENQUEUE_REPLENISH flag set,
which can guarantee that dl_throttled is reset in replenish_dl_entity().

This patch drops the resetting of throttled status in function
rt_mutex_setprio().

Thanks,

- Juri

> Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com>
> ---
>  kernel/sched/core.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 28b0d75..f1b9222 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -3037,7 +3037,6 @@ void rt_mutex_setprio(struct task_struct *p, int prio)
>  		if (!dl_prio(p->normal_prio) ||
>  		    (pi_task && dl_entity_preempt(&pi_task->dl, &p->dl))) {
>  			p->dl.dl_boosted = 1;
> -			p->dl.dl_throttled = 0;
>  			enqueue_flag = ENQUEUE_REPLENISH;
>  		} else
>  			p->dl.dl_boosted = 0;
> 


  reply	other threads:[~2015-04-21  8:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06  8:53 [PATCH 1/7] sched/deadline: fix try to pull pinned dl tasks in pull algorithm Wanpeng Li
2015-04-06  8:53 ` [PATCH 2/7] sched/deadline: make init_sched_dl_class() __init Wanpeng Li
2015-04-07 13:48   ` Juri Lelli
2015-04-07 23:00     ` Wanpeng Li
2015-04-06  8:53 ` [PATCH 3/7] sched/deadline: reduce rq lock contention by eliminating locking of non-feasible target Wanpeng Li
2015-04-07 13:48   ` Juri Lelli
2015-04-07 22:57     ` Wanpeng Li
2015-04-06  8:53 ` [PATCH 4/7] sched/deadline: reschedule if stop task slip in after pull operations Wanpeng Li
2015-04-20 10:27   ` Juri Lelli
2015-04-20 22:59     ` Wanpeng Li
2015-04-20 23:02       ` Wanpeng Li
2015-04-21  8:22         ` Juri Lelli
2015-04-06  8:53 ` [PATCH 5/7] sched/deadline: drop duplicate init_sched_dl_class declaration Wanpeng Li
2015-04-08  8:47   ` Juri Lelli
2015-04-08  8:33     ` Wanpeng Li
2015-04-06  8:53 ` [PATCH 6/7] sched/deadline: depend on clearing throttled status in replenish_dl_entity Wanpeng Li
2015-04-21  8:16   ` Juri Lelli [this message]
2015-04-21  8:10     ` Wanpeng Li
2015-04-06  8:53 ` [PATCH 7/7] sched/rt: reschedule if stop/dl task slip in after pull operations Wanpeng Li
2015-04-14 23:10 ` [PATCH 1/7] sched/deadline: fix try to pull pinned dl tasks in pull algorithm Wanpeng Li
2015-04-27  9:42 ` Wanpeng Li
2015-05-06  7:11   ` 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=5536076F.9020404@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;
as well as URLs for NNTP newsgroup(s).