From owner-freebsd-arch Sat Aug 18 3:10: 3 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 46F8637B409; Sat, 18 Aug 2001 03:09:56 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f7IAE4J10122; Sat, 18 Aug 2001 03:14:05 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108181014.f7IAE4J10122@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: Mike Smith , Amit Shah , freebsd-arch@FreeBSD.ORG Subject: Re: threaded device drivers In-reply-to: Your message of "Sat, 18 Aug 2001 01:17:50 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Aug 2001 03:14:04 -0700 From: Mike Smith 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 > 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. > Threads are not nearly lightweight enough yet to provide, say, offlevel > processing such as RSX-11 or VMS provided. Taskqueue does this well too. -- ... 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