From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bilbo.ozlabs.org (bilbo.ozlabs.org [203.10.76.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bilbo.ozlabs.org", Issuer "CAcert Class 3 Root" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 496E8DDF9F for ; Sat, 9 May 2009 13:31:28 +1000 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <18948.63755.279732.294842@cargo.ozlabs.ibm.com> Date: Sat, 9 May 2009 13:31:23 +1000 From: Paul Mackerras To: David Miller Subject: Re: question about softirqs In-Reply-To: <20090508.165358.97542490.davem@davemloft.net> References: <4A04B76D.20106@nortel.com> <18948.49541.735156.176919@cargo.ozlabs.ibm.com> <20090508.165358.97542490.davem@davemloft.net> Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , David Miller writes: > Grumble, when did that happen :-( Ages ago (i.e. before the switch to git :). Talk to Ingo, it's his doing IIRC. > That's horrible for latency compared to handling it directly > in the trap return path. Actually, I don't know why we ever let there be softirqs pending when we're in process context. I would think that we should just call do_softirq immediately if we raise a softirq when !in_interrupt(). But I might be missing some subtlety. Paul.