From owner-freebsd-arch Sat Aug 18 13:22:12 2001 Delivered-To: freebsd-arch@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 6864337B409; Sat, 18 Aug 2001 13:22:10 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f7IKM7I61050; Sat, 18 Aug 2001 13:22:07 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sat, 18 Aug 2001 13:22:07 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Christoph Hellwig Cc: Mike Smith , Amit Shah , freebsd-arch@FreeBSD.ORG Subject: Re: threaded device drivers In-Reply-To: <20010818220823.C8481@caldera.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 18 Aug 2001, Christoph Hellwig wrote: > 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. The linux schedule_task functions aren't all that lightweight either. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message