[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YoZMInrha8Sux61Q@lunn.ch>
Date: Thu, 19 May 2022 15:54:42 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Paolo Abeni <pabeni@...hat.com>
Cc: David Laight <David.Laight@...lab.com>,
'Pavan Chebbi' <pavan.chebbi@...adcom.com>,
Michael Chan <michael.chan@...adcom.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"mchan@...adcom.com" <mchan@...adcom.com>,
David Miller <davem@...emloft.net>
Subject: Re: tg3 dropping packets at high packet rates
> If the packet processing is 'bursty', you can have idle time and still
> hit now and the 'rx ring is [almost] full' condition. If pause frames
> are enabled, that will cause the peer to stop sending frames: drop can
> happen in the switch, and the local NIC will not notice (unless there
> are counters avaialble for pause frames sent).
You can control pause with ethtool
ethtool -a|--show-pause devname
ethtool -A|--pause devname [autoneg on|off] [rx on|off] [tx on|off]
But it depends on the driver implementing these options. So you might
want to try autoneg on, rx off, tx off, for testing.
ethtool should also show you want has been negotiated for pause, if
the driver has implemented that part of the ethtool API.
Andrew
Powered by blists - more mailing lists