Date: Sat, 18 Aug 2001 08:38:09 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: Mike Smith <msmith@FreeBSD.ORG> Cc: Amit Shah <amitshah@techie.com>, freebsd-arch@FreeBSD.ORG Subject: Re: threaded device drivers Message-ID: <Pine.BSF.4.21.0108180831400.59594-100000@beppo> In-Reply-To: <200108181014.f7IAE4J10122@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0108180831400.59594-100000>