From owner-freebsd-arch Sat Aug 18 12:50:10 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 66DFC37B413; Sat, 18 Aug 2001 12:50:08 -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 f7IJo5I60844; Sat, 18 Aug 2001 12:50:05 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sat, 18 Aug 2001 12:50:04 -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: <20010818214826.B8481@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 No, I'm perfectly happy with the current thread mechanism, which should improve over time. On Sat, 18 Aug 2001, Christoph Hellwig wrote: > On Sat, Aug 18, 2001 at 08:38:09AM -0700, Matthew Jacob wrote: > > No, that's not what I wanted to do. I wanted full process context that allows > > me to do tsleeps, etc., although it could probably done via a taskq mechanism > > if I went to the effort to rewrite it as a set of taskqueue calls while in > > 'rebuild' state. > > 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. > > 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