From: luca abeni <luca.abeni@unitn.it>
To: Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: Tommaso Cucinotta <tommaso.cucinotta@sssup.it>,
Juri Lelli <juri.lelli@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, linux-dl@retis.sssup.it
Subject: Re: [PATCH] sched/deadline: document behavior of sched_yield()
Date: Fri, 9 Sep 2016 14:24:10 +0200 [thread overview]
Message-ID: <20160909142410.5a442d2d@utopia> (raw)
In-Reply-To: <c8f85d23-f279-57c1-9daa-f5bda5d966e4@redhat.com>
On Fri, 9 Sep 2016 09:17:56 -0300
Daniel Bristot de Oliveira <bristot@redhat.com> wrote:
> On 09/09/2016 07:00 AM, luca abeni wrote:
> > Maybe instead of saying that the task is suspended you can say that
> > since the remaining runtime goes to 0 the task is immediately throttled,
> > and will be able to execute again only after the time is equal to the
> > scheduling deadline (as explained in "2. Scheduling algorithm").
>
> well, that is not true anymore. Since:
>
> 48be3a6 sched/deadline: Always calculate end of period on sched_yield()
>
> the runtime is zeroed at the replenishment, if dl_se->dl_yielded is set
> and runtime > 0.
Ok, but the task is still throttled, right?
Thanks,
Luca
next prev parent reply other threads:[~2016-09-09 12:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 20:09 [PATCH] sched/deadline: document behavior of sched_yield() Tommaso Cucinotta
2016-09-09 7:40 ` Juri Lelli
2016-09-09 8:44 ` Tommaso Cucinotta
2016-09-09 8:44 ` Tommaso Cucinotta
2016-09-09 10:00 ` luca abeni
2016-09-09 12:17 ` Daniel Bristot de Oliveira
2016-09-09 12:24 ` luca abeni [this message]
2016-09-09 12:31 ` Daniel Bristot de Oliveira
2016-09-09 12:38 ` luca abeni
2016-09-09 13:15 ` Daniel Bristot de Oliveira
2016-09-09 17:45 ` Tommaso Cucinotta
2016-09-09 17:45 ` Tommaso Cucinotta
2016-09-10 12:41 ` [tip:sched/core] sched/deadline: Document " tip-bot for Tommaso Cucinotta
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=20160909142410.5a442d2d@utopia \
--to=luca.abeni@unitn.it \
--cc=bristot@redhat.com \
--cc=juri.lelli@gmail.com \
--cc=linux-dl@retis.sssup.it \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tommaso.cucinotta@sssup.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.