<?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/106" />

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

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

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

		<published>2017-11-06T11:19:26+01:00</published>
		<id>http://localhost/viewtopic.php?t=106&amp;p=210#p210</id>
		<link href="http://localhost/viewtopic.php?t=106&amp;p=210#p210"/>
		<title type="html"><![CDATA[Probabilistic task model]]></title>

		
		<content type="html" xml:base="http://localhost/viewtopic.php?t=106&amp;p=210#p210"><![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 13]<br><br>Probabilistic task model.<br><br>There are a number of places where probabilistic (like) things pop up.<br><ul><li> unprivileged GRUB would require a per-task limit on allows overrun</li><li> measurement based WCET, typically results in a distribution of sorts</li><li> SoftRT many stream workloads that want to maximize machine utilization, lower WCET budget to increase efficiency but then rely on overrun / unused bandwidth reclaim to deal with peaks.</li></ul>If we extend the task model with 1 more variable that is a 'variance' on budget, for example a 0-sum limit on overrun (overrun is added to the sum, and underrun subtracted from the sum and is limited to [0,x]) can this be usefully employed by the scheduling function?<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>
