All of lore.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Andi Kleen <ak@suse.de>
Cc: Mike Kravetz <kravetz@us.ibm.com>,
	Davide Libenzi <davidel@xmailserver.org>,
	lse-tech@lists.sourceforge.net,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Lse-tech] Re: Real Time Runqueue
Date: Mon, 19 Nov 2001 10:32:23 -0800	[thread overview]
Message-ID: <3BF95037.EEE6F7C3@mvista.com> (raw)
In-Reply-To: <20011116154701.G1152@w-mikek2.des.beaverton.ibm.com> <Pine.LNX.4.40.0111161620050.998-100000@blue1.dev.mcafeelabs.com> <20011116163224.H1152@w-mikek2.des.beaverton.ibm.com> <20011119173022.A19740@wotan.suse.de>

Andi Kleen wrote:
> 
> On Fri, Nov 16, 2001 at 04:32:24PM -0800, Mike Kravetz wrote:
> > The reason I ask is that we went through the pains of a separate
> > realtime RQ in our MQ scheduler.  And yes, it does hurt the common
> > case, not to mention the extra/complex code paths.  I was hoping
> > that someone in the know could enlighten us as to how RT semantics
> > apply to SMP systems.  If the semantics I suggest above are required,
> > then it implies support must be added to any possible future
> > scheduler implementations.
> 
> It seems a lot of applications/APIs do not care about global RT semantics,
> but about RT semantics for groups of threads or processes (e.g. java
> or ada applications). Linux currently simulates this only for root
> and with a global runqueue. 

Why do you say only root?  Since the schedule type and priority are
inherited one only needs to be root to set the progenitors real time
priority.  Also, a programs priority/ schedule type can be set by
another (root) program without the target program being root.  I
routinely set inetd to real time, for example, to let telnet sessions
run at real time.

> I don't think it makes too much sense to have
> an global rt queue on a multi processor system, but there should be some
> way to define "scheduling groups" where rt semantics are followed inside.

Still, the customer is king.

> Such a scheduling group could be a clone flag or default to CLONE_VM for
> example for compatibility.  A scheduling group would also make it possible
> to support simple rt semantics for thread groups as non root.  Then one
> could run a rt queue per scheduling group, and simulate global rt run queue
> or per cpu rt run queue as needed by appropiate setup.

My first thought is that this is fairly high overhead to put in the
schedule path.  May be if I knew more....


-- 
George           george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/

  parent reply	other threads:[~2001-11-19 18:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16 20:20 Real Time Runqueue Mike Kravetz
2001-11-16 20:26 ` Richard Gooch
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:23           ` Richard Gooch
2001-11-19 19:07             ` Mike Kravetz
2001-11-19 18:32           ` george anzinger [this message]
2001-11-19 18:40             ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2001-11-16 22:41 Jesse Pollard
2001-11-17  8:41 ` [Lse-tech] " george anzinger

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=3BF95037.EEE6F7C3@mvista.com \
    --to=george@mvista.com \
    --cc=ak@suse.de \
    --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 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.