Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp2468547imd; Fri, 2 Nov 2018 11:57:08 -0700 (PDT) X-Google-Smtp-Source: AJdET5d4VU5bXLVFdnymmStA0OaD0PdlFZb26CRtr/aTXT6gi222Q9ZsolmjhGNV/5YcosjUFW61 X-Received: by 2002:a17:902:9f95:: with SMTP id g21-v6mr12842009plq.129.1541185028087; Fri, 02 Nov 2018 11:57:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541185028; cv=none; d=google.com; s=arc-20160816; b=OG7H0IX2f65zHU/7CQyKWp/Y5vRdcbX9UWt/wXTycmdUIz2fd29H5Q6V9q1fsejNN3 bZZCWQLFLIIWzzOe23QBRLDq1aPtwZZlSWY/20ueqd/rqbiOJ8ocXlDuMHPaaP3VYNFN L2+hqDbZ+5CEt1MFgJuXiP4xofsW4FQvayEEg4Qs7KjFbkWWllw1CbBpWm4DPyevOEgh EVmIi3pp4gSm/S2eRTQGBP37FNJ1jJ9NZ5SflIpN8s24QHmLWkZpPUzplTugPjMxd/iq BO7Wqx3Md7qwv95pTRQBnwqtLNRp8DXQUa5Z+i5q85TAvfZ24ryv3Gm/EhOmlUS5jMSi FaZA== 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 :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=OW20VcRFAcELiOxWcNunqlRsspgiVuZ061QupTCpwoU=; b=ZWLKWC9sR5omYuE9Mem2tS/aFkrZr2sIrkaYSR5q56k02maiv48iMzsKRKLZ+fRipy ajYu38ef2HOgde7KbS1ah9LAs9MOxHfid7Fn7O6XITvmbvLmKn9/oQmjV3EoVDzPoL0U B6+5b3GYxlgmE7RLfF1Xlj30S9mzeLPq/LVIMihSp23dfKVSYMZnpM6CVaDMSf38LI5o SB/PSW7xzu+P6XSOKSOSxLmLSYzhLO3YfJ8tVwx3vFzff04RSZEwmFo2JZc0fDBZz+T3 ULHaV70OMvZb3ciTbh8QiQnXBTu/PrpAN6osr8Lstwd2PsQ9feYuXh7IIsARU4rjH5qJ SLvA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=wAyEGcCD; 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 3-v6si13468005plp.388.2018.11.02.11.56.53; Fri, 02 Nov 2018 11:57:08 -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; dkim=pass header.i=@kernel.org header.s=default header.b=wAyEGcCD; 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 S1731346AbeKCED1 (ORCPT + 99 others); Sat, 3 Nov 2018 00:03:27 -0400 Received: from mail.kernel.org ([198.145.29.99]:59198 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726760AbeKCED0 (ORCPT ); Sat, 3 Nov 2018 00:03:26 -0400 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BEB7320848; Fri, 2 Nov 2018 18:55:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1541184910; bh=c8Oz7f92FIAipW12vN55H+etevvjiKidAs6earou8gQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=wAyEGcCDa6YHetfRlE3PyIUhPnF+EGKHK9EX+qUJypNKvNm8jfmMddOqDBDEbTpqy eXXXL0QzaYPyt/iO3AtDbdbJV6ZYjl77meKmj23/ablROnvvnkM/zk+8/wnIT+GZRC kffXESaP2eDXrWhMSx/TGpzOOGyHikXQ0476aIQ8= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Heiner Kallweit , "David S. Miller" Subject: [PATCH 4.14 126/143] r8169: fix NAPI handling under high load Date: Fri, 2 Nov 2018 19:35:11 +0100 Message-Id: <20181102182907.938987299@linuxfoundation.org> X-Mailer: git-send-email 2.19.1 In-Reply-To: <20181102182857.064326086@linuxfoundation.org> References: <20181102182857.064326086@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.14-stable review patch. If anyone has any objections, please let me know. ------------------ From: Heiner Kallweit [ Upstream commit 6b839b6cf9eada30b086effb51e5d6076bafc761 ] 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: Greg Kroah-Hartman --- 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 @@ -7579,17 +7579,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;