From owner-freebsd-arch Sat Nov 27 15:49:23 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 2AA6214D01 for ; Sat, 27 Nov 1999 15:49:20 -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 AAA13538 for ; Sun, 28 Nov 1999 00:49:19 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA55126 for freebsd-arch@freebsd.org; Sun, 28 Nov 1999 00:49:18 +0100 (MET) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id CF00714D01 for ; Sat, 27 Nov 1999 15:49:11 -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 PAA10321 for ; Sat, 27 Nov 1999 15:49:11 -0800 (PST) Date: Sat, 27 Nov 1999 15:49:11 -0800 (PST) From: Julian Elischer To: arch@freebsd.org Subject: Re: Threads stuff In-Reply-To: <19991127223909.22A511FCF@io.yi.org> 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 On Sat, 27 Nov 1999, Jake Burkholder wrote: > > Julian Elischer wrote: > > > > > > > As long as the UTS was informed of the time spent in the kernel (I suppose > > via the IO control block?) for each KSE, then that would probably be good > > enough. > > I've put a diagram up on my web page that tries to incorporate > some of these ideas. I haven't included the queue-ing, because > that seems basically agreed upon. [...] > I'm just going from what Daniel said about libc_r having > to get the time of day and set the interval timer in > order to do a context switch, which can probably be > done in one system call. Either the context can be > saved in userland, in which case the scheduler returns > normally, and does a longjmp or the equivalent, > or the thread could be resumed as part of the > system call. > I don't know what Danthiks but this has alot more involvement or the kernel and boundary crossing than I was envisionning. I will try make aset of diagrams that outline the state of various objects related to a thread at various stages.. Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message