The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: luca abeni <luca.abeni@unitn.it>,
	peterz@infradead.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com
Subject: Re: [PATCH v2] sched/deadline: remove useless param from setup_new_dl_entity
Date: Fri, 8 Jul 2016 12:32:11 +0100	[thread overview]
Message-ID: <20160708113211.GA22074@e106622-lin> (raw)
In-Reply-To: <20160707094727.2de1a950@gandalf.local.home>

On 07/07/16 09:47, Steven Rostedt wrote:
> On Thu, 7 Jul 2016 09:39:09 +0100
> Juri Lelli <juri.lelli@arm.com> wrote:
> 
>  
> > > Having a better look at this is in my TODO list... But I still need to
> > > find some time :)
> > >   
> > 
> > Same here. No spare cycles right now to have a thorough look at this. :(
> 
> All in all, this should not hold up the current patch set. Maybe mark
> it with a "TODO" and try to remember to look into it at another time.

Added to my TODO list (right after reviewing Luca's reclaiming bits next
version and fix the cpuset issue :/) and posted v3.

> The chances that we are switching from a SCHED_OTHER/RT to DEADLINE
> that is already boosted is extremely rare. It can happen, but it's not
> critical enough to hold this up.
> 

Thanks,

- Juri

  reply	other threads:[~2016-07-08 11:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29 19:07 [PATCH v2] sched/deadline: remove useless param from setup_new_dl_entity Juri Lelli
2016-07-04  9:03 ` luca abeni
2016-07-04  9:28   ` Juri Lelli
2016-07-05  7:37 ` Wanpeng Li
2016-07-05  8:52   ` Juri Lelli
2016-07-05 14:20 ` Steven Rostedt
2016-07-05 14:39   ` Juri Lelli
2016-07-05 16:47     ` Steven Rostedt
2016-07-05 16:58       ` Juri Lelli
2016-07-06  8:44         ` luca abeni
2016-07-07  8:39           ` Juri Lelli
2016-07-07 13:47             ` Steven Rostedt
2016-07-08 11:32               ` Juri Lelli [this message]
2016-07-06  8:46   ` luca abeni

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=20160708113211.GA22074@e106622-lin \
    --to=juri.lelli@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@unitn.it \
    --cc=mingo@redhat.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