public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Juri Lelli <juri.lelli@arm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org, mingo@redhat.com,
	luca.abeni@unitn.it
Subject: Re: [PATCH] sched/deadline: remove useless param from setup_new_dl_entity
Date: Mon, 27 Jun 2016 17:52:29 +0200	[thread overview]
Message-ID: <20160627155229.GE30909@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160617162837.GQ5981@e106622-lin>

On Fri, Jun 17, 2016 at 05:28:37PM +0100, Juri Lelli wrote:
> On 17/06/16 09:49, Steven Rostedt wrote:
> > On Fri, 17 Jun 2016 10:48:41 +0100
> > Juri Lelli <juri.lelli@arm.com> wrote:
> > 
> > > setup_new_dl_entity() takes two parameters, but it only actually uses
> > > one of them to setup a new dl_entity.
> > > 
> > 
> > Actually this patch is making it so that setup_new_dl_entity() only
> > uses one of the parameters. Can you note why that change happened.
> > Because this change log implies that the second parameter wasn't used
> > before this patch, and that is incorrect.
> > 
> 
> True, but we were practically already using the same parameter, under a
> different name though, after
> 
> 2f9f3fdc928 "sched/deadline: Remove dl_new from struct sched_dl_entity"
> 
> as we currently do:
> 
>   setup_new_dl_entity(&p->dl, &p->dl)
> 
> > This patch reverts part of the change done in
> > commit 2d3d891d334 "sched/deadline: Add SCHED_DEADLINE inheritance
> > logic"
> > 
> 
> Before Luca's change we were doing
> 
>  setup_new_dl_entity(dl_se, pi_se)
> 
> in update_dl_entity() for a dl_se->new entity. So, I guess the question
> is actually why we wanted to use pi_se's parameters (the potential PI
> donor) for setting up a new entity? Maybe we broke the situation where a
> task is currently boosted by a DEADLINE waiter and we swich the holder
> to DEADLINE?
> 
> > It would be nice to have the reason in the change log.
> > 
> 
> Thanks a lot for pointing out what might be more than inaccuracy in the
> changelog.

Will you be reposting with a new Changelog?

  parent reply	other threads:[~2016-06-27 15:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  9:48 [PATCH] sched/deadline: remove useless param from setup_new_dl_entity Juri Lelli
2016-06-17  9:58 ` luca abeni
2016-06-17 10:08   ` Juri Lelli
2016-06-17 13:49 ` Steven Rostedt
2016-06-17 16:28   ` Juri Lelli
2016-06-17 20:15     ` luca abeni
2016-06-17 20:36       ` luca abeni
2016-06-27 15:52     ` Peter Zijlstra [this message]
2016-06-27 17:24       ` Juri Lelli

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=20160627155229.GE30909@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=juri.lelli@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@unitn.it \
    --cc=mingo@redhat.com \
    --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