From owner-freebsd-arch Sat Aug 18 12:59:18 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 D320F37B405; Sat, 18 Aug 2001 12:53:55 -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 f7IJuJS00930; Sat, 18 Aug 2001 12:56:20 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108181956.f7IJuJS00930@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Christoph Hellwig Cc: Matthew Jacob , Mike Smith , Amit Shah , freebsd-arch@FreeBSD.ORG Subject: Re: threaded device drivers In-reply-to: Your message of "Sat, 18 Aug 2001 21:48:26 +0200." <20010818214826.B8481@caldera.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Aug 2001 12:56:19 -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 > 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 allo > ws > > me to do tsleeps, etc., although it could probably done via a taskq mechani > sm > > 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. But entirely unnecessary, since we can already create threads in the kernel, as I pointed out earlier. See the kthread* family of functions. -- ... 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