From owner-freebsd-current Fri Sep 19 20:15:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA28911 for current-outgoing; Fri, 19 Sep 1997 20:15:11 -0700 (PDT) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA28902 for ; Fri, 19 Sep 1997 20:15:08 -0700 (PDT) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id WAA02980; Fri, 19 Sep 1997 22:15:03 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id WAA15250; Fri, 19 Sep 1997 22:14:32 -0500 Message-ID: <19970919221431.23526@right.PCS> Date: Fri, 19 Sep 1997 22:14:31 -0500 From: Jonathan Lemon To: Terry Lambert Cc: Nate Williams , current@FreeBSD.ORG Subject: Re: FYI: regarding our rfork(2) References: <199709191956.NAA20377@rocky.mt.sri.com> <199709192210.PAA08418@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199709192210.PAA08418@usr06.primenet.com>; from Terry Lambert on Sep 09, 1997 at 10:10:13PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 09, 1997 at 10:10:13PM +0000, Terry Lambert wrote: > This is an unsatisfying soloution, mostly because kernel > threads block on blocking calls from user threads. This > means that I can only ever have N blocking calls outstanding, > and a total of (M-N) threads, which are ready to run will > not get quantum, regardless of the scheduling class used. What about other kernel/user thread implementations? Eg: scheduler activations, as put forth by Anderson, et.al. From what they describe, there is no limit to the number of blocking calls a user-level process can make. Unfortunately, I feel that they have glossed over some of the implementation details in their paper, making it difficult to evaluate. -- Jonathan