Date: Sat, 18 Aug 2001 22:08:23 +0200 From: Christoph Hellwig <hch@caldera.de> To: Mike Smith <msmith@FreeBSD.ORG> Cc: Christoph Hellwig <hch@caldera.de>, Matthew Jacob <mjacob@feral.com>, Amit Shah <amitshah@techie.com>, freebsd-arch@FreeBSD.ORG Subject: Re: threaded device drivers Message-ID: <20010818220823.C8481@caldera.de> In-Reply-To: <200108181956.f7IJuJS00930@mass.dis.org>; from msmith@FreeBSD.ORG on Sat, Aug 18, 2001 at 12:56:19PM -0700 References: <20010818214826.B8481@caldera.de> <200108181956.f7IJuJS00930@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 18, 2001 at 12:56:19PM -0700, Mike Smith wrote: > > You might want to take a look at Linux's schedule_task family of cuntions > > (kernel/context.c) - it should be straight forward to implement for FreeBSD. > > But entirely unnecessary, since we can already create threads in the > kernel, as I pointed out earlier. See the kthread* family of functions. I know kthread ;) The differnce is just that you need an entire thread this way - threads are eating up far too much ressources (e.g. kernel stack) for certain types of problems. A way to just execute some function in user context is a very nice appropeach for lots of the smaller stuff. Some people might also remeber NetWare's WorkToDo's that can do this stuff combines with wait queues. Christoph -- Christoph Hellwig Kernel Engineer Unix/Linux Integration Caldera Deutschland GmbH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010818220823.C8481>