Date: Sat, 18 Aug 2001 14:22:05 -0700 From: Mike Smith <msmith@freebsd.org> To: Christoph Hellwig <hch@caldera.de> Cc: Mike Smith <msmith@FreeBSD.ORG>, Matthew Jacob <mjacob@feral.com>, Amit Shah <amitshah@techie.com>, freebsd-arch@FreeBSD.ORG Subject: Re: threaded device drivers Message-ID: <200108182122.f7ILM5S01713@mass.dis.org> In-Reply-To: Your message of "Sat, 18 Aug 2001 22:08:23 %2B0200." <20010818220823.C8481@caldera.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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.
Er. Yeah, whatever. 8)
> 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.
... which is basically what taskqueue is.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
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?200108182122.f7ILM5S01713>