From owner-freebsd-arch Sat Aug 18 8:38: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 7992737B401; Sat, 18 Aug 2001 08:38: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 f7IFc9I59641; Sat, 18 Aug 2001 08:38:09 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sat, 18 Aug 2001 08:38:09 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Mike Smith Cc: Amit Shah , freebsd-arch@FreeBSD.ORG Subject: Re: threaded device drivers In-Reply-To: <200108181014.f7IAE4J10122@mass.dis.org> 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, Mike Smith wrote: > > An example of this is the QLogic driver (isp(4)) spawns a thread that is used > > to rebuild loop state and rescan the loop and fabric port databases after an > > asynchronous event brings a notification of change. > > You can do this with the taskqueue mechanism too; since you have a > notification event. 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. > > > Threads are not nearly lightweight enough yet to provide, say, offlevel > > processing such as RSX-11 or VMS provided. > > Taskqueue does this well too. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message