Date: Tue, 28 Jan 2003 11:07:02 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Robert Watson <rwatson@FreeBSD.ORG> Cc: Julian Elischer <julian@elischer.org>, Jeff Roberson <jroberson@chesapeake.net>, Steve Kargl <sgk@troutmask.apl.washington.edu>, Gary Jennejohn <garyj@jennejohn.org>, arch@FreeBSD.ORG Subject: Re: New scheduler - Interactivity fixes Message-ID: <200301281907.h0SJ72tA028159@apollo.backplane.com> References: <Pine.NEB.3.96L.1030128111454.87213G-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
It seems to me that the correct solution is to use the SYSINIT mechanism
to allow multiple schedulers to be loaded into the kernel, and choose
one as a default (aka sched_4bsd) either with a flag in the SYSINIT or
simply by order.
Then a boot variable could be used to override the default and allow
one to choose a particular scheduler.
The work required to do this is minor. We need only structuralize /
vectorize the few global procedures in sched_*() and then declare
them static.
-Matt
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?200301281907.h0SJ72tA028159>