From owner-freebsd-current@FreeBSD.ORG Tue Nov 11 01:16:41 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 EE79216A4D0; Tue, 11 Nov 2003 01:16:41 -0800 (PST) Received: from herring.nlsystems.com (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4745E43F75; Tue, 11 Nov 2003 01:16:40 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from [10.0.0.2] (herring.nlsystems.com [10.0.0.2]) hAB9EEvf029025; Tue, 11 Nov 2003 09:14:58 GMT (envelope-from dfr@nlsystems.com) From: Doug Rabson To: Alex Wilkinson In-Reply-To: <20031110233914.GC14579@squirm.dsto.defence.gov.au> References: <20031110051010.GC33733@elvis.mu.org> <1068454923.21784.1.camel@herring.nlsystems.com> <20031110233914.GC14579@squirm.dsto.defence.gov.au> Content-Type: text/plain Message-Id: <1068542054.24997.2.camel@herring.nlsystems.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Tue, 11 Nov 2003 09:14:14 +0000 Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on herring.nlsystems.com cc: dfr@freebsd.org cc: Alfred Perlstein cc: current@freebsd.org Subject: Re: taskqueue patch 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, 11 Nov 2003 09:16:42 -0000 On Mon, 2003-11-10 at 23:39, Alex Wilkinson wrote: > On Mon, Nov 10, 2003 at 09:02:03AM +0000, Doug Rabson wrote: > > I wasn't involved in converting taskqueue from 4.x-style SWIs to kernel > threads so I can't be sure but this does look reasonable. I've been > wondering about the 'not exiting' diagnostic from init for a while > myself. > > Hi Doug, > > What are "SWIs" ? Its an ancient VAX concept - 'SoftWare Interrupts'. Basically on a vax, you could poke a register and it would cause a low-priority interrupt. They were often used for 'split priority' interrupt handlers where you did the minimum amount of work in the first interrupt and then triggered a SWI for the rest. The advantage being that the SWI could be pre-empted by another high-priority hardware interrupt.