From owner-freebsd-smp Thu Dec 21 11:18:31 2000 From owner-freebsd-smp@FreeBSD.ORG Thu Dec 21 11:18:29 2000 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 2F29D37B400; Thu, 21 Dec 2000 11:18:29 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eBLJIT610621; Thu, 21 Dec 2000 11:18:29 -0800 (PST) Date: Thu, 21 Dec 2000 11:18:28 -0800 From: Alfred Perlstein To: John Baldwin Cc: Julian Elischer , smp@FreeBSD.org, archie@FreeBSD.org Subject: Re: looking for locking advice.. Message-ID: <20001221111828.X19572@fw.wintelcom.net> References: <20001221105710.U19572@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Thu, Dec 21, 2000 at 11:12:02AM -0800 Sender: bright@fw.wintelcom.net Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * John Baldwin [001221 11:12] wrote: > > On 21-Dec-00 Alfred Perlstein wrote: > > * John Baldwin [001221 10:47] wrote: > >> > >> On 21-Dec-00 Alfred Perlstein wrote: > >> > I wouldn't worry all too much about the distiction between interrupt > >> > execution state versus non-interrupt. Sure device nodes want to complete > >> > as soon as possible, however eventually we'll have _multiple_ software > >> > interrupt threads running on each processor so latency is reduced. > >> > >> > ps ax | grep 'swi[0-9]' | wc -l > >> 7 > >> > >> We already have multiple software interrupt threads that can run > >> concurrently. > >> :) > > > > But not in the same class though, right? > > > > You can't more than one network software inetrrupt running atm, no? > > You could if you wanted. Just create multiple threads via sinthand_add() and > schedule them with sched_swi(). (Yes, this is another namespace I'm going to > fix0r). *nod*, we'll really want to run at least one of each interrupt class on each cpu most likely otherwise the network stack remains serialized based on only having a single scheduleable interrupt thread. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message