Date: Tue, 29 Jun 1999 00:39:41 +0800 From: Peter Wemm <peter@netplex.com.au> 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: <19990628163941.221D483@overcee.netplex.com.au> In-Reply-To: Your message of "Mon, 28 Jun 1999 08:26:02 CST." <199906281426.IAA15234@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh wrote:
> In message <XFMail.990628173909.darius@dons.net.au> "Daniel J. O'Connor" writ
es:
> : I don't suppose someone could post an explanation of how kernel threads wor
k
> : could they? :)
>
> Looks like it just does a fork like thing so it can do context
> switches...
>
> Warner
When I looked last time, it was effectively a callable interface to what we
do from SYSINIT_KT(), ie: fork proc0, which runs in kernel space with it's
own stack etc.
kthread_create_deferred() is not really anything to do with those sort of
threads. It's just a generic callback registration system that happens to
be called after the basic processes have started so that proc0,1,2 etc are
not disturbed. It's similar to the config_intrhook() stuff but is run
later.
You can probably cut/paste our SYSINIT_KT() code into some compatable
function interfaces pretty easily to avoid yet another new file.
Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
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?19990628163941.221D483>