From owner-freebsd-current@FreeBSD.ORG Mon Aug 25 22:36:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D566E16A4BF; Mon, 25 Aug 2003 22:36:47 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id E80FD43FE3; Mon, 25 Aug 2003 22:36:44 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id h7Q5aiYU005728; Mon, 25 Aug 2003 23:36:44 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id h7Q5aYDm005721; Mon, 25 Aug 2003 23:36:34 -0600 (MDT) (envelope-from ken) Date: Mon, 25 Aug 2003 23:36:34 -0600 From: "Kenneth D. Merry" To: Nate Lawson Message-ID: <20030826053634.GA5646@panzer.kdm.org> References: <20030825134756.P18344@root.org> <20030826002949.GA3136@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030826002949.GA3136@panzer.kdm.org> User-Agent: Mutt/1.4.1i cc: stable@freebsd.org cc: current@freebsd.org Subject: Re: scsi-da does not work with INVARIANTS (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2003 05:36:48 -0000 On Mon, Aug 25, 2003 at 18:29:49 -0600, Kenneth D. Merry wrote: > On Mon, Aug 25, 2003 at 13:49:30 -0700, Nate Lawson wrote: > > Ken is aware of the following problem. It is in both cd(4) and da(4) as > > well as stable and current. One possible approach would be to run > > {da,cd}register() from a task queue and not at interrupt time. > > That would be tricky, since the peripheral registration process currently > expects a success/failure return from the peripheral constructor. > > Just putting the sysctl creation in a task queue, though, would not be too > difficult. > > One question I have, though, is whether task queues run in a thread context > or not. If not, then we'll have the same problem. The answer is -- the currently defined task queues use software interrupts. If it is possible to create a task queue that uses a kernel thread instead, that might be a generally useful thing. (And it might solve this particular issue.) Ken -- Kenneth Merry ken@kdm.org