The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Byungchul Park <byungchul.park@lge.com>
To: Juri Lelli <juri.lelli@arm.com>
Cc: <peterz@infradead.org>, <mingo@kernel.org>,
	<linux-kernel@vger.kernel.org>, <juri.lelli@gmail.com>,
	<rostedt@goodmis.org>, <kernel-team@lge.com>
Subject: Re: [PATCH v3] sched/deadline: Change the time to replenish runtime for sleep tasks
Date: Wed, 1 Mar 2017 21:09:39 +0900	[thread overview]
Message-ID: <20170301120939.GI11663@X58A-UD3R> (raw)
In-Reply-To: <20170301095933.GV19665@e106622-lin>

On Wed, Mar 01, 2017 at 09:59:33AM +0000, Juri Lelli wrote:
> I'd err on the side of clearness and safety (where I assume the current
> code is safer only because it has been tested for a while :). However,
> if you can prove in a reproducible manner that the changes you are
> proposing make overhead way smaller, we might still consider them.

Then.. I will check how much it reduces the overhead.

> Anyway, IMVHO, there are still lot of known issues and missing features
> that deserve time; so, if your have some time to look at DEADLINE stuff,
> I'd kindly point you at
> 
> https://github.com/jlelli/sched-deadline/wiki/TODOs
> 
> You would be very welcome if you think you can pick something of what
> above up, and we should synchronize in that case, as several people are
> already working on some of the aforementioned bits.

Why not? I would be very honored if I can work together.

To be honest with you, I'm currently developing another patch set about
task migration in dl/rt. I will let you know after making it clear.

Unfortunately I have little time until 19th Mar, so I can do my work and
your TODOs after the day. I will continue the works after the day. :)

Thank you very much,
Byungchul

      reply	other threads:[~2017-03-01 12:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23  6:14 [PATCH v3] sched/deadline: Change the time to replenish runtime for sleep tasks Byungchul Park
2017-02-23 10:11 ` Byungchul Park
2017-02-28 11:35 ` Juri Lelli
2017-02-28 13:09   ` Byungchul Park
2017-02-28 17:47     ` Juri Lelli
2017-03-01  3:37       ` Byungchul Park
2017-03-01  9:59         ` Juri Lelli
2017-03-01 12:09           ` Byungchul Park [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=20170301120939.GI11663@X58A-UD3R \
    --to=byungchul.park@lge.com \
    --cc=juri.lelli@arm.com \
    --cc=juri.lelli@gmail.com \
    --cc=kernel-team@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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