Date: Mon, 28 Jun 1999 17:41:33 +0930 (CST) From: "Daniel J. O'Connor" <doconnor@gsoft.com.au> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: hackers@FreeBSD.ORG, Warner Losh <imp@harmony.village.org>, Julian Elischer <julian@whistle.com> Subject: Re: "restricted" kernel threads implementation from NetBSD via n Message-ID: <XFMail.990628173909.darius@dons.net.au> In-Reply-To: <199906280719.AAA18001@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990628173909:1295=_ Content-Type: text/plain; charset=us-ascii On 28-Jun-99 Matthew Dillon wrote: > I think we desparately need a kernel threads implementation. *Any* > implementation, so we can start messing around with it! Even if it isn't > the one we eventually choose. I don't suppose someone could post an explanation of how kernel threads work could they? :) I sort of grasp the idea but I'm wondering what passes for context switches and stuff like that.. What does the switching between threads etc? Or am I completely off track? --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990628173909:1295=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN3ctpWj0TqzKxF7VAQE5uAP/SDvpI6TZJuDt0FfHfe0Eqp90QD2gjk2R nTrDhLsP/vMey3Ogsc/LeFNww8woaqXwTD6x3i+04wzkoDvti7rlczi4+2DUfnAj 79lflMw7DdBgd9tYB/3+QTQ3o2BVpT2JZK8zHVX5cPiPKHcPwQl7DhojQeqBx0QU W7ZKnn2ZYqI= =SXMo -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990628173909:1295=_-- End of MIME 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?XFMail.990628173909.darius>