From owner-freebsd-arch Sat Aug 18 1:18:14 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 E1F7C37B40C; Sat, 18 Aug 2001 01:18:11 -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 f7I8HoI55273; Sat, 18 Aug 2001 01:17:50 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sat, 18 Aug 2001 01:17:50 -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: <200108180808.f7I88mJ08635@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 > > In -current, drivers that want threads can spawn them off; where it's > absolutely necessary it's usually a driver-specific issue rather than > being something that could be implemented in any more generic a fashion. > 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. Threads are not nearly lightweight enough yet to provide, say, offlevel processing such as RSX-11 or VMS provided. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message