Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2975146imu; Sun, 9 Dec 2018 14:04:59 -0800 (PST) X-Google-Smtp-Source: AFSGD/VppGwKn6MN93CDiSBlEyQFCP8167r433c4mSeVB4zkaMiA8ede5ZAHHr+ulaG/fxGtLmQT X-Received: by 2002:a63:b218:: with SMTP id x24mr8553130pge.223.1544393099423; Sun, 09 Dec 2018 14:04:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544393099; cv=none; d=google.com; s=arc-20160816; b=HeaB3+RRod9gACJl4NV3SseLOFD1J7JdK8QmU/GBFgZl2GajWK7nnL+9qFBiln1+Jk qB8OEEPsOPuFyAIfJYQZQuFKQuT84+cAR7hnVRZ7gZn4/7qg8anlWPoonqIDRZTc8n5n st+r0w2UuioAeAklnSHuSE4MiH0d9URWndwgz7sY/40bplEpRnnGSugxz47BTt/uRovJ uKf1RoxwtiY7YWl4QT68dWoDiz5ARJ+g3fPu8MiAkXCC93F60cHdoARNXkTd6QSRuAvd oheILB8TETKQggHEEhbyusuEPKyfQFijR11NDQsC/wmrT1Zk/RfwsvWaZnXIy5zJgpDb /kJw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition; bh=Mb6wqXhGK1ABu5ijAtQWEiTB6fVjfW9lZ3RzoIVoqj4=; b=PisKu6cDvR1hEcwnLGUL4vL+8iYbv+OmKAX44yFXX9Cjdsyu8pSQdRh01qbLwvsC0i XJShFOaySxwpjAerCg9lrsWP43xLIBJiL9BE3LQGV2I/+TX97LXLgausozAyiAvz9VYI CvOoxVgLaIWNX6gN0txeWwmyXAdK87iJZ/4piukoPaNJpPf7N33K2zW6NoJh9n+OMA09 tToe4xxNC9tomflj/0HwR0L0JdSmk5DvB9wV9Fw3xMFEthX4eLYko6qAEL9pPkeGq5e3 7iKoyZN0MwrTCJht06Sm160nHg483UwXB5NK6Gfo3zKrap9pVPvGNz4wLwTfF9iCWfmA fYcw== 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 x10si7945031pgl.209.2018.12.09.14.04.44; Sun, 09 Dec 2018 14:04:59 -0800 (PST) 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 S1726716AbeLIWDX (ORCPT + 99 others); Sun, 9 Dec 2018 17:03:23 -0500 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:35682 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726602AbeLIVz2 (ORCPT ); Sun, 9 Dec 2018 16:55:28 -0500 Received: from pub.yeoldevic.com ([81.174.156.145] helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gW72q-0002ia-UQ; Sun, 09 Dec 2018 21:55:25 +0000 Received: from ben by deadeye with local (Exim 4.91) (envelope-from ) id 1gW72l-0003h8-IG; Sun, 09 Dec 2018 21:55:19 +0000 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, "David S. Miller" , "Heiner Kallweit" Date: Sun, 09 Dec 2018 21:50:33 +0000 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) X-Patchwork-Hint: ignore Subject: [PATCH 3.16 318/328] r8169: fix NAPI handling under high load In-Reply-To: X-SA-Exim-Connect-IP: 81.174.156.145 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.62-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Heiner Kallweit commit 6b839b6cf9eada30b086effb51e5d6076bafc761 upstream. rtl_rx() and rtl_tx() are called only if the respective bits are set in the interrupt status register. Under high load NAPI may not be able to process all data (work_done == budget) and it will schedule subsequent calls to the poll callback. rtl_ack_events() however resets the bits in the interrupt status register, therefore subsequent calls to rtl8169_poll() won't call rtl_rx() and rtl_tx() - chip interrupts are still disabled. Fix this by calling rtl_rx() and rtl_tx() independent of the bits set in the interrupt status register. Both functions will detect if there's nothing to do for them. Fixes: da78dbff2e05 ("r8169: remove work from irq handler.") Signed-off-by: Heiner Kallweit Signed-off-by: David S. Miller Signed-off-by: Ben Hutchings --- drivers/net/ethernet/realtek/r8169.c | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) --- a/drivers/net/ethernet/realtek/r8169.c +++ b/drivers/net/ethernet/realtek/r8169.c @@ -6417,17 +6417,15 @@ static int rtl8169_poll(struct napi_stru struct rtl8169_private *tp = container_of(napi, struct rtl8169_private, napi); struct net_device *dev = tp->dev; u16 enable_mask = RTL_EVENT_NAPI | tp->event_slow; - int work_done= 0; + int work_done; u16 status; status = rtl_get_events(tp); rtl_ack_events(tp, status & ~tp->event_slow); - if (status & RTL_EVENT_NAPI_RX) - work_done = rtl_rx(dev, tp, (u32) budget); + work_done = rtl_rx(dev, tp, (u32) budget); - if (status & RTL_EVENT_NAPI_TX) - rtl_tx(dev, tp); + rtl_tx(dev, tp); if (status & tp->event_slow) { enable_mask &= ~tp->event_slow;