mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Mike Kravetz <kravetz@us.ibm.com>
Cc: lse-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	Davide Libenzi <davidel@xmailserver.org>
Subject: Re: Real Time Runqueue
Date: Fri, 16 Nov 2001 13:26:21 -0700	[thread overview]
Message-ID: <200111162026.fAGKQLM03728@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20011116122005.E1152@w-mikek2.des.beaverton.ibm.com>
In-Reply-To: <20011116122005.E1152@w-mikek2.des.beaverton.ibm.com>

Mike Kravetz writes:
> As you may know, a few of us are experimenting with multi-runqueue
> scheduler implementations.  One area of concern is where to place
> realtime tasks.  It has been my assumption, that POSIX RT semantics
> require a specific ordering of tasks such as SCHED_FIFO and SCHED_RR.
> To accommodate this ordering, I further believe that the simplest
> solution is to ensure that all realtime tasks reside on the same
> runqueue.  In our MQ scheduler we have a separate runqueue for all
> realtime tasks.  The problem is that maintaining a separate realtime
> runqueue is a pain and results in some fairly complex/ugly code.
> 
> Since I'm not a realtime expert, I would like to ask if my assumption
> about strict ordering of RT tasks is accurate.  Also, is anyone aware
> of other ways to approach this problem?

Yes, strict ordering is required. Years ago I championed a separate
runqueue for RT tasks. Linus even said he liked the approach. I got
busy and never nursed it to inclusion. The patch is here:
ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/kernel-patches/v2.1/rtqueue-patch

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  reply	other threads:[~2001-11-16 20:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16 20:20 Mike Kravetz
2001-11-16 20:26 ` Richard Gooch [this message]
2001-11-16 22:44 ` Davide Libenzi
2001-11-16 23:47   ` Mike Kravetz
2001-11-17  0:28     ` Davide Libenzi
2001-11-17  0:32       ` Mike Kravetz
2001-11-17  8:08         ` [Lse-tech] " george anzinger
2001-11-19 20:23           ` Matthew Dobson
2001-11-19 15:15         ` Victor Yodaiken
2001-11-19 16:30         ` [Lse-tech] " Andi Kleen
2001-11-19 17:06           ` Davide Libenzi
2001-11-19 18:32           ` george anzinger
2001-11-19 18:40             ` Andi Kleen
2001-11-19 18:23         ` Richard Gooch
2001-11-19 19:07           ` Mike Kravetz
2001-11-16 22:41 Jesse Pollard
2001-11-17  0:13 ` Davide Libenzi

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=200111162026.fAGKQLM03728@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=davidel@xmailserver.org \
    --cc=kravetz@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®