From mboxrd@z Thu Jan 1 00:00:00 1970 From: Song Liu Subject: Re: [PATCH net 00/15] netpoll: avoid capture effects for NAPI drivers Date: Mon, 24 Sep 2018 21:18:13 +0000 Message-ID: References: <20180921222752.101307-1-edumazet@google.com> <20180923.220440.434897583339366571.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: David Miller , netdev , Michael Chan , Ariel Elior , Eric Dumazet , Tariq Toukan , Saeed Mahameed , Jeff Kirsher , Jakub Kicinski , Jay Vosburgh , Veaceslav Falico , Andy Gospodarek To: Eric Dumazet Return-path: Received: from mx0a-00082601.pphosted.com ([67.231.145.42]:47882 "EHLO mx0a-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727531AbeIYDWh (ORCPT ); Mon, 24 Sep 2018 23:22:37 -0400 In-Reply-To: Content-Language: en-US Content-ID: Sender: netdev-owner@vger.kernel.org List-ID: > On Sep 24, 2018, at 2:05 PM, Eric Dumazet wrote: >=20 >>=20 >> Interesting, maybe a bnxt specific issue. >>=20 >> It seems their model is to process TX/RX notification in the same queue, >> they throw away RX events if budget =3D=3D 0 >>=20 >> It means commit e7b9569102995ebc26821789628eef45bd9840d8 is wrong and >> must be reverted. >>=20 >> Otherwise, we have a possibility of blocking a queue under netpoll press= ure. >=20 > Hmm, actually a revert might not be enough, since code at lines 2030-2031 > would fire and we might not call napi_complete_done() anyway. >=20 > Unfortunately this driver logic is quite complex. >=20 > Could you test on other NIC eventually ? >=20 It actually runs OK on ixgbe.=20 @Michael, could you please help us with this?=20 Thanks, Song