From owner-freebsd-arch@FreeBSD.ORG Thu Aug 11 07:07:04 2005 Return-Path: X-Original-To: freebsd-arch@freebsd.org 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 E670316A41F; Thu, 11 Aug 2005 07:07:04 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (delight.idiom.com [216.240.32.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9E6643D46; Thu, 11 Aug 2005 07:07:04 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id 599812165C2; Thu, 11 Aug 2005 00:07:04 -0700 (PDT) Received: from [192.168.2.2] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id j7B7738i097077; Thu, 11 Aug 2005 00:07:03 -0700 (PDT) (envelope-from julian@elischer.org) Message-ID: <42FAF913.40101@elischer.org> Date: Thu, 11 Aug 2005 00:06:59 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050424 X-Accept-Language: en, hu MIME-Version: 1.0 To: gnn@freebsd.org References: <42F9ECF2.8080809@freebsd.org> <200508100911.50004.jhb@FreeBSD.org> <20050810.162006.48492066.imp@bsdimp.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: Special schedulers, one CPU only kernel, one only userland X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2005 07:07:05 -0000 gnn@freebsd.org wrote: > But, the question, which is interesting to me for other reasons > (namely putting in various real-time schedulers) was not answered. Do > we currently have the requisite primitives to implement different > schedulers or is there still a lot of jiggery/pokery required? An attempt was made to create a scheduler API (see sched.h) As it has only been used for 4BSD and ULE we do not yet know how successful the abstraction was, but theoretically it shouldbe relatively easy to slot in a different scheduler. Anything that is missing probably should be added. > > Thanks, > George > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"