linux-kernel - Re: [RFC 4/4] Documentation/scheduler/sched-deadline.txt: add some references

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]

Message-ID: <20150408144304.GH5029@twins.programming.kicks-ass.net>
Date:	Wed, 8 Apr 2015 16:43:04 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Luca Abeni <lucabe72@...il.com>
Cc:	henrik@...tad.us, juri.lelli@...il.com, raistlin@...ux.it,
	mingo@...nel.org, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org, Luca Abeni <luca.abeni@...tn.it>
Subject: Re: [RFC 4/4] Documentation/scheduler/sched-deadline.txt: add some
 references

On Wed, Apr 08, 2015 at 01:59:40PM +0200, Luca Abeni wrote:
> + As seen, enforcing that the total utilisation is smaller than M does not
> + guarantee that global EDF schedules the tasks without missing any deadline
> + (in other words, global EDF is not an optimal scheduling algorithm). However,
> + a total utilisation smaller than M is enough to guarantee that non real-time
> + tasks are not starved and that the tardiness of real-time tasks has an upper
> + bound[12] (as previously noticed). Different bounds on the maximum tardiness

                             ^^^ noted?

> + experienced by real-time tasks have been developed in various papers[13,14],
> + but the theoretical result that is important for SCHED_DEADLINE is that if
> + the total utilisation is smaller or equal than M then the response times of
> + the tasks are limited.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/