From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr ([192.134.164.83]:51893 "EHLO mail2-relais-roc.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751014Ab3HNPTL (ORCPT ); Wed, 14 Aug 2013 11:19:11 -0400 Date: Wed, 14 Aug 2013 17:18:51 +0200 (CEST) From: Julia Lawall Subject: Re: question about netif_rx In-Reply-To: Message-ID: References: <20130811155640.GA10070@electric-eye.fr.zoreil.com> <20130813052036.GA11640@electric-eye.fr.zoreil.com> <20130813204131.GA4696@electric-eye.fr.zoreil.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: devicetree-owner@vger.kernel.org To: Rami Rosen Cc: Francois Romieu , David Shwatrz , Julia Lawall , grant.likely@linaro.org, rob.herring@calxeda.com, Netdev , "linux-kernel@vger.kernel.org" , devicetree@vger.kernel.org List-ID: On Wed, 14 Aug 2013, Rami Rosen wrote: > Hi, > BTW, this is not the only NAPI issue here. When looking into cleanup > of resources in this driver, a call to netif_napi_del() is missing > (though there is a call to napi_disable(), which is not enough for > proper cleanup). Actually, netif_napi_del seems to be quite underused. At least approximately, I would assume that every file that uses netif_napi_add should use netif_napi_del at least once, and possible more times. But I find 118 .c files that use netif_napi_add, and only 35 that use netif_napi_del. Are there some cases where it might not be needed? julia