From owner-freebsd-smp Thu Oct 5 18:34:55 2000 Delivered-To: freebsd-smp@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 1279037B502 for ; Thu, 5 Oct 2000 18:34:52 -0700 (PDT) Received: (qmail 98454 invoked by uid 1142); 6 Oct 2000 01:34:51 -0000 Date: 5 Oct 2000 18:34:51 -0700 Date: Thu, 5 Oct 2000 16:08:13 -0700 From: Jason Evans To: Warner Losh Cc: John Baldwin , smp@FreeBSD.org Subject: Re: Releasing interrupts? Message-ID: <20001005160813.R58256@canonware.com> References: <200010051918.NAA01346@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200010051918.NAA01346@harmony.village.org>; from imp@village.org on Thu, Oct 05, 2000 at 01:18:42PM -0600 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Oct 05, 2000 at 01:18:42PM -0600, Warner Losh wrote: > In message John Baldwin writes: > : You may be able to orchestrate a way to have your thread call kthread_exit(), > : which would work. The person to bug for a kthread_cancel() is Peter though. > : :) > > OK. kthread_exit() is likely sufficient for my needs in NEWCARD. I > can queue a poison pill as easily as I can queue an INSERT or REMOVED > event :-) Good to hear it. With regard to thread cancellation, it's another example of a feature that, if used, usually indicates poor program design, so I hope that we don't find a need for kthread_cancel(). Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message