From owner-freebsd-arch Tue Jan 28 11:49:26 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 0759337B401 for ; Tue, 28 Jan 2003 11:49:26 -0800 (PST) Received: from net1.gendyn.com (gate1.gendyn.com [204.60.171.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06BB743F3F for ; Tue, 28 Jan 2003 11:49:24 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from [153.11.11.3] (helo=ebnext01) by net1.gendyn.com with esmtp (Exim 2.12 #1) id 18dbjI-000CVJ-00 for arch@freebsd.org; Tue, 28 Jan 2003 14:49:08 -0500 Received: from clcrtr.gdeb.com ([153.11.109.11]) by ebnext01 with SMTP id h0SJn8oC015896 for ; Tue, 28 Jan 2003 14:49:08 -0500 Received: from vigrid.com (gpz.clc.gdeb.com [192.168.3.12]) by clcrtr.gdeb.com (8.11.4/8.11.4) with ESMTP id h0Q41BN18968 for ; Sat, 25 Jan 2003 23:01:12 -0500 (EST) (envelope-from eischen@vigrid.com) Message-ID: <3E36DEB1.8CC4E61F@vigrid.com> Date: Tue, 28 Jan 2003 14:49:05 -0500 From: Daniel Eischen X-Mailer: Mozilla 4.78 [en] (X11; U; SunOS 5.9 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: arch@freebsd.org Subject: New scheduler and classes Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 How does the new scheduler/API handle different classes? If you want to have processes^Wthreads in 3 or 4 different scheduling classes (perhaps real-time, time-sharing, etc, a la Solaris), how does "a scheduler" handle this? Is there only ever one scheduler selected in the kernel, and it is up to this scheduler to handle all the threads in each class? Or can you stack schedulers somehow, so that each class gets its own scheduler, and it's up to the top-level scheduler to schedule amongst the classes? -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message