From owner-freebsd-arch Wed Jan 29 1:49:50 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 696AD37B401; Wed, 29 Jan 2003 01:49:49 -0800 (PST) Received: from cirb503493.alcatel.com.au (c18609.belrs1.nsw.optusnet.com.au [210.49.80.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75A9743E4A; Wed, 29 Jan 2003 01:49:48 -0800 (PST) (envelope-from peterjeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.5/8.12.5) with ESMTP id h0T9niLZ027852; Wed, 29 Jan 2003 20:49:44 +1100 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost) by cirb503493.alcatel.com.au (8.12.6/8.12.5/Submit) id h0T9nhoT027851; Wed, 29 Jan 2003 20:49:43 +1100 (EST) Date: Wed, 29 Jan 2003 20:49:43 +1100 From: Peter Jeremy To: Robert Watson Cc: Jeff Roberson , arch@FreeBSD.ORG Subject: Re: New scheduler - Interactivity fixes Message-ID: <20030129094943.GA27833@cirb503493.alcatel.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jan 28, 2003 at 11:29:14AM -0500, Robert Watson wrote: > scheduler 4bsd > #scheduler ule > >Config(8) could be taught to allow at most one scheduler directive. It >would allow zero with a warning ("No scheduler defined at compile-time; >one must be loaded as a module"). We'd either introduce a new class >similar to OPTIONS, or map the argument of scheduler directly to an >option, with the possible risk of getting some false positives in the >argument validity checking. Traditionally, this is done by having the linker whinge about undefined or multiply defined symbols when it tries to link the kernel, leaving the poor user to try and guess which option he got wrong :-). I'd prefer to allow multiple schedulers to be compiled in (or KLD'd), with a sysctl to select which one (preferably alterable at runtime). This reduces(?) the problem to: - ensure that at least one scheduler is present before trying to use it - picking a default scheduler when multiple schedulers are present. >(For the humor impaired, we could also use "sched" instead of "scheduler" >above.) Maybe we should name all the schedulers after colours. "Blue" seems logical for Jeff's new scheduler. How about "red" for the standard one? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message