<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
	<link rel="self" type="application/atom+xml" href="http://localhost/app.php/feed/topic/105" />

	<title>Tools and Benchmarks for Real-Time Systems</title>
	<subtitle>ECRTS Community Forum</subtitle>
	<link href="http://localhost/index.php" />
	<updated>2017-11-06T11:13:58+01:00</updated>

	<author><name><![CDATA[Tools and Benchmarks for Real-Time Systems]]></name></author>
	<id>http://localhost/app.php/feed/topic/105</id>

		<entry>
		<author><name><![CDATA[Sophie Quinton]]></name></author>
		<updated>2017-11-06T11:13:58+01:00</updated>

		<published>2017-11-06T11:13:58+01:00</published>
		<id>http://localhost/viewtopic.php?t=105&amp;p=209#p209</id>
		<link href="http://localhost/viewtopic.php?t=105&amp;p=209#p209"/>
		<title type="html"><![CDATA[Support for single CPU affinity in G-EDF]]></title>

		
		<content type="html" xml:base="http://localhost/viewtopic.php?t=105&amp;p=209#p209"><![CDATA[
[This problem was presented by Peter Zijlstra during his <a href="http://www.ecrts.org/index.php?id=284" class="postlink">ECRTS'17 keynote talk</a>, see slide 11]<br><br>Support for single CPU affinity in G-EDF (also see the open problem "An alternative admission test for G-EDF"). The expected behaviour of single CPU affinity is that of UP where people 'know' EDF to be optimal. That is, there is an expectation of stricter deadlines.<br><br>The 'obvious' hierarchical approach 'local EDF + G-EDF' has issues in that there are fairly trivial task sets that will have (avoidable) deadline misses. The question is, can we do better in a single scheduling function.<br><br>The proposal (by me), is to combine EDF and LLF. The observation is that, given the deadline constrained sporadic task model:<br><br>  e_i &lt;= d_i &lt;= p_i<br><br>and discarding the degenerate case of e_i == d_i == p_i, we're left with a model that has at least 2 degrees of freedom (implicit deadline has d_i == p_i) and EDF only employs 1, namely d_i.<br><br>This leaves us freedom to differentiate between local and global tasks.<br><br>Define laxity_i := d_i - e_i ; when i is a local task, inf. otherwise.<br><br>Then:  t + e_EDF &lt; d_LLF - e_LLF -&gt; EDF, otherwise LLF<br><br>That is, avoid the EDF pick from causing negative laxity.<br><br>Similar to EDZL (as pointed out by Luca); can any of that analysis be reused? Marko thought there might be EDZL variants that relax the 0-laxity thing.<p>Statistics: Posted by <a href="http://localhost/memberlist.php?mode=viewprofile&amp;u=55">Sophie Quinton</a> — Mon Nov 06, 2017</p><hr />
]]></content>
	</entry>
	</feed>
