From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from viefep18-int.chello.at (viefep18-int.chello.at [62.179.121.38]) by ozlabs.org (Postfix) with ESMTP id DBE67DDF93 for ; Tue, 12 May 2009 19:32:45 +1000 (EST) Subject: Re: question about softirqs From: Peter Zijlstra To: Ingo Molnar In-Reply-To: <20090512092348.GA29796@elte.hu> References: <18948.63755.279732.294842@cargo.ozlabs.ibm.com> <20090508.234815.127227651.davem@davemloft.net> <4A086DB2.8040703@nortel.com> <20090511.162436.193717082.davem@davemloft.net> <4A08C62F.1050105@nortel.com> <20090512081237.GA16403@elte.hu> <1242119578.11251.321.camel@twins> <20090512092348.GA29796@elte.hu> Content-Type: text/plain Date: Tue, 12 May 2009 11:32:41 +0200 Message-Id: <1242120761.11251.324.camel@twins> Mime-Version: 1.0 Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org, Steven Rostedt , paulus@samba.org, Thomas Gleixner , David Miller List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2009-05-12 at 11:23 +0200, Ingo Molnar wrote: > > Yeah, that would be "nice". A single IRQ thread plus the process > context(s) doing networking might perform well. > > Multiple IRQ threads (softirq and hardirq threads mixed) i'm not so > sure about - it's extra context-switching cost. Sure, that was implied by the getting rid of softirqs ;-), on -rt we currently suffer this hardirq/softirq thread ping-pong, it sucks.