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 4557CB7063 for ; Sun, 8 Nov 2009 20:08:29 +1100 (EST) Date: Sun, 08 Nov 2009 01:08:48 -0800 (PST) Message-Id: <20091108.010848.116517157.davem@davemloft.net> To: avorontsov@ru.mvista.com Subject: Re: [PATCH RFC] gianfar: Do not call skb recycling with disabled IRQs From: David Miller In-Reply-To: <20091105165738.GA31923@oksana.dev.rtsoft.ru> References: <20091105165738.GA31923@oksana.dev.rtsoft.ru> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Cc: jdl@jdl.com, netdev@vger.kernel.org, linuxppc-dev@ozlabs.org, afleming@freescale.com, jason.wessel@windriver.com, shemminger@vyatta.com, buytenh@wantstofly.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Anton Vorontsov Date: Thu, 5 Nov 2009 19:57:38 +0300 > But that basically means that with skb recycling we can't safely > use KGDBoE, though we can add something like this: Please stop adding special logic only to your driver to handle these things. Either it's a non-issue, or it's going to potentially be an issue for everyone using skb_recycle_check() in a NAPI driver, right? So why not add the "in_interrupt()" or whatever check to skb_recycle_check() and if the context is unsuitable return false (0) ok?