Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp4680437imm; Mon, 17 Sep 2018 19:35:52 -0700 (PDT) X-Google-Smtp-Source: ANB0VdbCGAlmDSTb15WW0yf7lFFvwylPOeh9kXmAnmBnsn0NTcl8fMefNj4SAScLT5fqnKuyteCY X-Received: by 2002:a62:1605:: with SMTP id 5-v6mr28475867pfw.11.1537238152873; Mon, 17 Sep 2018 19:35:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537238152; cv=none; d=google.com; s=arc-20160816; b=PsG4nMYtytx2JOyCK+tlOv7+z75b4YQnL8XMw62m399dM5rPjYGFC7lfuDm/R6OQpm bpqqucnGmrgLelR+s1heh2cgy0VF/jD3MYGD9+VQANqX3Q5CLwInpoFS33Pk43RPFZzU xh5w+AdgoroUe+QBL9fR9Z2ho7KuQ535HKMWCBj4O8szyKIQLVgOo+P/mJjI5+UaRkQQ Q3v9kNzJzGaNq+akgFcfHep3fTGJ0QwDV6vR1tWxE5DSkYUc3xpfuRLMgMrhrQrV07zJ z5bFt1PTF/L4b6aikQF8YirgeB4+ofEIXiYMeFnuP5OzLG3qoMWrL2oxTHaiBFCQYKM+ ANhQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=KMg2pr+IccGBdTxv0Cfdv6cS8aiFD1IH9Ov8WI2fQPQ=; b=kqfVwMUbRt64Dv9HqC8nNjTsAqJMKcIZY+IazFctqT9w4DpEwu9XeZk6UuCpYwABmN 2KNJ+mJUFXSlFge03aVifpjwaoHoxnW6Hw7NBATJrMHOWRsVRkTkjr45sWvUeJwpqfP6 51QMjOIS5NhLmoOz7WqpxE6KpBMk3kXov2Rw++QyuL4pT4ctTzY65uyWYvGAX75+lcjz O6g/p+RoXtbLFS522v1a6ORjCqrIRLVqB7MQsU+1mG7BHyudM/emkt7yOtwaQAajiFgo wuooLN/kmbAQqhCnGnrTNHbgS8hqkRBfgZLdpJvL/YAiZZh5APmtpN+3lCEmWt8XSQ+Q 0UUQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x22-v6si16637678pfh.84.2018.09.17.19.35.37; Mon, 17 Sep 2018 19:35:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727544AbeIRIFt (ORCPT + 99 others); Tue, 18 Sep 2018 04:05:49 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:54400 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726501AbeIRIFs (ORCPT ); Tue, 18 Sep 2018 04:05:48 -0400 Received: from localhost (unknown [104.240.4.228]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id E1E5A146228E0; Mon, 17 Sep 2018 19:35:31 -0700 (PDT) Date: Mon, 17 Sep 2018 19:35:31 -0700 (PDT) Message-Id: <20180917.193531.1424852853827678152.davem@davemloft.net> To: ahs3@redhat.com Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, isubramanian@apm.com, kchudgar@apm.com, qnguyen@apm.com Subject: Re: [PATCH] net: apm: xgene: force XGene enet driver to re-balance IRQ usage From: David Miller In-Reply-To: <20180917233533.28626-1-ahs3@redhat.com> References: <20180917233533.28626-1-ahs3@redhat.com> X-Mailer: Mew version 6.7 on Emacs 26 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Mon, 17 Sep 2018 19:35:32 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Al Stone Date: Mon, 17 Sep 2018 17:35:33 -0600 > @@ -866,8 +866,11 @@ static int xgene_enet_napi(struct napi_struct *napi, const int budget) > processed = xgene_enet_process_ring(ring, budget); > > if (processed != budget) { > + struct irq_desc *desc = irq_to_desc(ring->irq); > + > napi_complete_done(napi, processed); > - enable_irq(ring->irq); > + if (desc && desc->depth > 0) > + enable_irq(ring->irq); I really can't accept a patch that grovels into IRQ layer internals to work around a driver's IRQ enable/disable usage problem. Sorry.