Date: Mon, 28 Jun 1999 09:28:11 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Warner Losh <imp@harmony.village.org> Cc: "Daniel J. O'Connor" <doconnor@gsoft.com.au>, hackers@FreeBSD.ORG Subject: Re: "restricted" kernel threads implementation from NetBSD via n Message-ID: <Pine.BSF.3.95.990628092421.10211C-100000@current1.whistle.com> In-Reply-To: <199906281426.IAA15234@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 28 Jun 1999, Warner Losh wrote: > In message <XFMail.990628173909.darius@dons.net.au> "Daniel J. O'Connor" writes: > : I don't suppose someone could post an explanation of how kernel threads work > : could they? :) > > Looks like it just does a fork like thing so it can do context > switches... To be more precise, it should be more like a rfork() like thing that doesn't change any resources except the stack, a process structure and processor context. Specifically, processor VMspace is basically left at whatever it is already at, and there is no 'signal' stuff or file descriptor table munging. We might even allow the MMU to be left unchanged too. julian > > Warner > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.990628092421.10211C-100000>