From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sunset.davemloft.net (74-93-104-97-Washington.hfc.comcastbusiness.net [74.93.104.97]) by ozlabs.org (Postfix) with ESMTP id 85B01DDFA4 for ; Wed, 13 May 2009 15:28:54 +1000 (EST) Date: Tue, 12 May 2009 22:28:48 -0700 (PDT) Message-Id: <20090512.222848.152842353.davem@davemloft.net> To: paulus@samba.org Subject: Re: question about softirqs From: David Miller In-Reply-To: <18954.22390.754419.803434@cargo.ozlabs.ibm.com> References: <20090512092348.GA29796@elte.hu> <20090512.214427.193728136.davem@davemloft.net> <18954.22390.754419.803434@cargo.ozlabs.ibm.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Cc: a.p.zijlstra@chello.nl, linuxppc-dev@ozlabs.org, netdev@vger.kernel.org, rostedt@goodmis.org, mingo@elte.hu, tglx@linutronix.de List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Paul Mackerras Date: Wed, 13 May 2009 15:15:34 +1000 > David Miller writes: > >> I fully expected us to be, at this point, talking about putting the >> pending softirq check back into the trap return path :-/ > > Would that actually do any good, in the case where the system has > decided that ksoftirqd is handling soft irqs at the moment? Even if ksoftirqd is running, we check and run pending softirqs from trap return. Sure, I imagine we could re-enter this "ksoftirq blocked by highprio thread" situation if we get flooded every single time over and over again.