linux-kernel - Re: [PATCH] sched/deadline: document behavior of sched

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 9 Sep 2016 09:17:56 -0300
From:   Daniel Bristot de Oliveira <bristot@...hat.com>
To:     luca abeni <luca.abeni@...tn.it>,
        Tommaso Cucinotta <tommaso.cucinotta@...up.it>
Cc:     Juri Lelli <juri.lelli@...il.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
        linux-dl@...is.sssup.it
Subject: Re: [PATCH] sched/deadline: document behavior of sched_yield()

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.

-- Daniel