All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Bastoni <bastoni@cs.unc.edu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Bjoern Brandenburg <bbb@email.unc.edu>,
	Raistlin <raistlin@linux.it>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Song Yuan <song.yuan@ericsson.com>,
	Dmitry Adamushko <dmitry.adamushko@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Nicola Manica <nicola.manica@disi.unitn.it>,
	Luca Abeni <lucabe72@email.it>,
	Claudio Scordino <claudio@evidence.eu.com>,
	Harald Gustafsson <harald.gustafsson@ericsson.com>,
	Giuseppe Lipari <lipari@retis.sssup.it>
Subject: Re: periods and deadlines in SCHED_DEADLINE
Date: Tue, 03 Aug 2010 23:53:15 -0400	[thread overview]
Message-ID: <4C58E42B.40000@cs.unc.edu> (raw)
In-Reply-To: <1280828775.1923.447.camel@laptop>

On 08/03/2010 05:46 AM, Peter Zijlstra wrote:
> On Sun, 2010-07-11 at 08:42 +0200, Bjoern Brandenburg wrote:
>> If you want to do G-EDF with limited and different budgets on each CPU
>> (e.g., G-EDF tasks may only run for 100 out of 1000 ms on CPU 0, but
>> for 400 out of 1000 ms on CPU 1), then you are entering the domain of
>> restricted-supply scheduling, which is significantly more complicated
>> to analyze (see [1,2]).
> 
> Would making the thing homogenious by assuming the worst for all cpus
> make the analysis easier? That is, in the above example, only allow the
> G-EDF scheduler to run for 100 out of 1000 ms on both cpus.

Both [1,2] (and also [4]) assumes a more general model than the one based on the worst for all
CPUs, therefore the analysis (based on these papers) will likely be more pessimistic, but not
necessarily easier.

- Andrea

[4] E. Bini, M. Bertogna, S. Baruah, Virtual Multiprocessor Platforms: Specification and Use. In
Proceedings of the 2009 30th IEEE Real-Time Systems Symposium, 437-446, 2009.

-- 
Andrea Bastoni
Visiting Ph.D. Student
Dept. of Computer Science
University of North Carolina at Chapel Hill
http://www.sprg.uniroma2.it/home/bastoni/

  reply	other threads:[~2010-08-04  4:38 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-09 13:38 periods and deadlines in SCHED_DEADLINE Raistlin
2010-07-09 14:18 ` Peter Zijlstra
2010-07-09 14:51   ` Bjoern Brandenburg
2010-07-09 16:35     ` Peter Zijlstra
2010-07-10  9:01       ` Raistlin
2010-07-10 10:28         ` Peter Zijlstra
2010-07-10 14:49           ` Raistlin
2010-07-11  6:42         ` Bjoern Brandenburg
2010-08-03  9:41           ` Peter Zijlstra
2010-08-04  3:52             ` Andrea Bastoni
2010-08-04  7:14               ` Peter Zijlstra
2010-08-04  5:18             ` Bjoern Brandenburg
2010-08-03  9:46           ` Peter Zijlstra
2010-08-04  3:53             ` Andrea Bastoni [this message]
2010-08-04  5:02             ` Bjoern Brandenburg
2010-07-10  7:08     ` Raistlin
2010-07-11  6:46       ` Bjoern Brandenburg
2010-08-03  8:16         ` Peter Zijlstra
2010-08-03 11:42           ` Gregory Haskins
2010-08-04  6:30           ` Bjoern Brandenburg
2010-07-09 14:24 ` Peter Zijlstra
2010-07-10  7:11   ` Luca Abeni
2010-07-10 10:36     ` Peter Zijlstra
2010-07-11  6:12       ` Bjoern Brandenburg
2010-07-09 14:30 ` Peter Zijlstra
2010-07-10  9:14   ` Raistlin
2010-07-10 17:19   ` Harald Gustafsson
2010-07-10 18:31     ` Peter Zijlstra
2010-07-10 20:08       ` Harald Gustafsson
2010-07-10 21:52         ` Raistlin
2010-07-11  5:41           ` Harald Gustafsson
2010-07-11  7:32         ` Bjoern Brandenburg
2010-07-12 10:21           ` Harald Gustafsson
2010-08-04  5:55             ` Bjoern Brandenburg
2010-08-02 19:34           ` Peter Zijlstra
2010-08-04  4:44             ` Bjoern Brandenburg
2010-07-09 14:32 ` Peter Zijlstra
2010-07-10  7:50   ` Raistlin
2010-07-10 15:11     ` Peter Zijlstra
2010-07-10 17:29       ` Harald Gustafsson
2010-07-11  6:15     ` Bjoern Brandenburg
2010-07-10  7:09 ` Luca Abeni
2010-07-10  9:20   ` Raistlin

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=4C58E42B.40000@cs.unc.edu \
    --to=bastoni@cs.unc.edu \
    --cc=bbb@email.unc.edu \
    --cc=claudio@evidence.eu.com \
    --cc=dmitry.adamushko@gmail.com \
    --cc=harald.gustafsson@ericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lipari@retis.sssup.it \
    --cc=lucabe72@email.it \
    --cc=nicola.manica@disi.unitn.it \
    --cc=peterz@infradead.org \
    --cc=raistlin@linux.it \
    --cc=song.yuan@ericsson.com \
    --cc=tglx@linutronix.de \
    /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.