All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Baker <baker@cs.fsu.edu>
To: raj@ece.cmu.edu, jayhawk@soe.ucsc.edu, a.p.zijlstra@chello.nl,
	raistlin@linux.it, niehaus@ittc.ku.edu, henrik@austad.us,
	linux-kernel@vger.kernel.org, mingo@elte.hu, billh@gnuppy.monk
Cc: baker.tlh@comcast.net
Subject: Re: [Fwd: Re: RFC for a new Scheduling policy/class in the Linux-kernel]
Date: Mon, 26 Apr 2010 07:56:58 -0400	[thread overview]
Message-ID: <20100426115658.GA21346@cs.fsu.edu> (raw)

I have not seen any more e-mail on this.  How is it going?  Is there any
chance of rolling in some corrections for the SCHED_SPORADIC treatment?  In
particular, could we have a DO_NOT_RUN priority, that is guaranteed to
prevent a task from running at all?

For more detail, see http://ww2.cs.fsu.edu/~stanovic/papers/rtas10.pdf .

Ted

WARNING: multiple messages have this Message-ID (diff)
From: Ted Baker <baker@cs.fsu.edu>
To: raj@ece.cmu.edu, jayhawk@soe.ucsc.edu, a.p.zijlstra@chello.nl,
	raistlin@linux.it, niehaus@ittc.ku.edu, henrik@austad.us,
	linux-kernel@vger.kernel.org, mingo@elte.hu,
	billh@gnuppy.monkey.org, linux-rt-users@vger.kernel.org,
	fabio@gandalf.sssup.it, anderson@cs.unc.edu, tglx@linutronix.de,
	dhaval.giani@gmail.com, cucinotta@sssup.it,
	lipari@retis.sssup.it
Cc: baker.tlh@comcast.net
Subject: Re: [Fwd: Re: RFC for a new Scheduling policy/class in the Linux-kernel]
Date: Mon, 26 Apr 2010 07:56:58 -0400	[thread overview]
Message-ID: <20100426115658.GA21346@cs.fsu.edu> (raw)

I have not seen any more e-mail on this.  How is it going?  Is there any
chance of rolling in some corrections for the SCHED_SPORADIC treatment?  In
particular, could we have a DO_NOT_RUN priority, that is guaranteed to
prevent a task from running at all?

For more detail, see http://ww2.cs.fsu.edu/~stanovic/papers/rtas10.pdf .

Ted

             reply	other threads:[~2010-04-26 12:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 11:56 Ted Baker [this message]
2010-04-26 11:56 ` [Fwd: Re: RFC for a new Scheduling policy/class in the Linux-kernel] Ted Baker
2010-04-26 18:29 ` Joerg Roedel
2010-04-26 18:37   ` Doug Niehaus
2010-05-03 14:41 ` Peter Zijlstra
2010-05-03 15:54   ` Ted Baker
2010-05-03 16:13   ` Ted Baker
  -- strict thread matches above, loose matches on Subject: below --
2009-07-16 19:41 Raj Rajkumar
     [not found] <4A5F7254.3020809@ece.cmu.edu>
2009-07-16 19:18 ` James H. Anderson
     [not found]   ` <4A5F806D.6040701@ece.cmu.edu>
2009-07-16 19:46     ` James H. Anderson
2009-07-16 20:47       ` Raj Rajkumar

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=20100426115658.GA21346@cs.fsu.edu \
    --to=baker@cs.fsu.edu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=baker.tlh@comcast.net \
    --cc=billh@gnuppy.monk \
    --cc=henrik@austad.us \
    --cc=jayhawk@soe.ucsc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=niehaus@ittc.ku.edu \
    --cc=raistlin@linux.it \
    --cc=raj@ece.cmu.edu \
    /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.