Date: Tue, 31 Jul 2001 20:40:34 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Julian Elischer <julian@elischer.org> Cc: arch@FreeBSD.ORG Subject: Re: thread scheduling question Message-ID: <Pine.SUN.3.91.1010731202724.16986A-100000@pcnet1.pcnet.com> In-Reply-To: <Pine.BSF.4.21.0107311606470.35786-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 31 Jul 2001, Julian Elischer wrote:
> hmmm, ok.. so, as a redux:
>
> KSE's in the original KSEG are affected (the original KSEG is
> affected. New KSEGs created after this, are affected (by default)
> exisiting other KSEGs are not affected..
Hmm, after reading more carefully, I don't think that _subsequent_
KSEGs created for _system_ scope threads should inherit the same
scheduling parameters. Read this part a little more carefully:
> > The underlying kernel scheduled entities for the process
> > contention scope threads will have their scheduling parame-
> > ters changed to the value specified in param. Kernel
> > scheduled entities for use by process contention scope
^^^^^^^^^^^^^^^^^^^^^^^^^
> > threads that are created after this call completes inherit
> > their scheduling policy and associated scheduling parameters
> > from the process.
It doesn't say that KSEs (yes, nice terminology ;-)) created for
_system_ scope threads inherit the scheduling policy/parameters.
Since we (currently) don't create more than one KSEG for process
scope threads, this degenerates into just affecting the original
KSEG. I suppose that if the threads library ever wanted to create
more than 1 KSEG for process scope threads, we could just pass a
flags word with KSEG_SCHED_INHERIT set on kseg_create().
--
Dan Eischen
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.1010731202724.16986A-100000>