From owner-freebsd-arch Sat Oct 12 9:25:32 2002 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 B5B3A37B401; Sat, 12 Oct 2002 09:25:31 -0700 (PDT) Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BA7D43EB1; Sat, 12 Oct 2002 09:25:30 -0700 (PDT) (envelope-from hiten@angelica.unixdaemons.com) Received: from angelica.unixdaemons.com (hiten@localhost.unixdaemons.com [127.0.0.1]) by angelica.unixdaemons.com (8.12.5/8.12.1) with ESMTP id g9CGPCc8020374; Sat, 12 Oct 2002 12:25:12 -0400 (EDT) X-Authentication-Warning: angelica.unixdaemons.com: Host hiten@localhost.unixdaemons.com [127.0.0.1] claimed to be angelica.unixdaemons.com Received: (from hiten@localhost) by angelica.unixdaemons.com (8.12.5/8.12.1/Submit) id g9CGPBNl020373; Sat, 12 Oct 2002 12:25:11 -0400 (EDT) (envelope-from hiten) Date: Sat, 12 Oct 2002 12:25:11 -0400 From: Hiten Pandya To: Terry Lambert Cc: Jeff Roberson , Jeff Roberson , arch@FreeBSD.ORG Subject: Re: Scheduler patch, ready for commit. Message-ID: <20021012122510.A13430@angelica.unixdaemons.com> References: <20021010022058.A23516-100000@mail.chesapeake.net> <3DA537E4.274A3714@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3DA537E4.274A3714@mindspring.com>; from tlambert2@mindspring.com on Thu, Oct 10, 2002 at 01:18:44AM -0700 X-Operating-System: FreeBSD i386 X-Public-Key: http://www.pittgoth.com/~hiten/pubkey.asc X-URL: http://www.unixdaemons.com/~hiten X-PGP: http://pgp.mit.edu:11371/pks/lookup?search=Hiten+Pandya&op=index 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 Thu, Oct 10, 2002 at 01:18:44AM -0700, Terry Lambert wrote the words in effect of: > > Yes, I agree, this is an important next step. I'm thinking that the > > scheduler should indicate how much space is needed to the proc allocation > > code. This much extra space could be allocated, and a pointer to > > scheduler specific data could really be a pointer within that allocated > > structure. This way it might be near enough for processor caches to be > > effective. Clearly this needs more work. That is outside of the scope of > > the current patch though. > > [...] > You may actually want to look at the Solaris/SVR4 implementation, > which supports both scheduling classes as loadable modules, and > simultaneous multiple scheduler classes (SVID III(RT) and the > "fixed" scheduling class, used to improve interactive response of > the X server, as well as a batch scheduler, are included in the > defaults for both systems). FWIW, the Solaris Internals book discusses this topic of scheduler classes in detail, IIRC. It has been time since I touched the book. Cheers. -- Hiten Pandya http://www.unixdaemons.com/~hiten hiten@unixdaemons.com, hiten@uk.FreeBSD.org, hiten@softweyr.com PGP: http://pgp.mit.edu:11371/pks/lookup?search=Hiten+Pandya&op=index To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message