From owner-freebsd-arch Wed Nov 10 12:30:31 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id DBF9414D71 for ; Wed, 10 Nov 1999 12:30:10 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id VAA14763 for ; Wed, 10 Nov 1999 21:30:08 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA08345 for freebsd-arch@freebsd.org; Wed, 10 Nov 1999 21:30:08 +0100 (MET) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 3113415141 for ; Wed, 10 Nov 1999 12:28:31 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id MAA60402 for ; Wed, 10 Nov 1999 12:28:29 -0800 (PST) Date: Wed, 10 Nov 1999 12:28:26 -0800 (PST) From: Julian Elischer To: freebsd-arch@freebsd.org Subject: Threads thread Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry, Archie and I are all at a class this week and have very poor connectivity. (I only have connectivity actually IN class) ;-) I was hoping that someone else could make take on the task of making an independent summary of things we discussed. My summary of 'goals' needs to be updated to include the ability to create 'groups' of threads, and for those groups to have the capability of being assigned separate system resource limits (e.g. different priority). This comes in two parts.. from the kernel's point of view, there must be different classes (groups) of KSE's (Kernel Schedulable Entities), But it is completely opaque to the kernel which User level Thread (ULT?) the User level thread scheuler assignes to those KSEs. One would hope that the ULS would co-operate! It seems to me that from the goals we have decided upon we are already seeing some facets of teh implementation becoming clear. Certainly we need Multiple KSEs and the ability of these to be grouped. We also need a ULS (user level Scheduler). What else can we see are becoming 'Inevitable'? Do we allow the thread system to schedule different threads when a thread get's a pagefault? How can we be sure that teh pagefault is not inteh scheduler? etc. etc. Julian (typing on a pretty slow link in class when I should be taking notice of the teacher) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message