[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM9PR04MB8397D4DEDFCE75487195762A96C89@AM9PR04MB8397.eurprd04.prod.outlook.com>
Date: Wed, 11 May 2022 08:17:49 +0000
From: Claudiu Manoil <claudiu.manoil@....com>
To: Vladimir Oltean <vladimir.oltean@....com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Eric Dumazet <edumazet@...gle.com>,
Vinicius Costa Gomes <vinicius.gomes@...el.com>,
Michael Walle <michael@...le.cc>,
Xiaoliang Yang <xiaoliang.yang_1@....com>,
Po Liu <po.liu@....com>
Subject: RE: [PATCH net-next 2/2] net: enetc: count the tc-taprio window drops
> -----Original Message-----
> From: Vladimir Oltean <vladimir.oltean@....com>
> Sent: Tuesday, May 10, 2022 7:36 PM
[...]
> Subject: [PATCH net-next 2/2] net: enetc: count the tc-taprio window drops
>
> From: Po Liu <Po.Liu@....com>
>
> The enetc scheduler for IEEE 802.1Qbv has 2 options (depending on
> PTGCR[TG_DROP_DISABLE]) when we attempt to send an oversized packet
> which will never fit in its allotted time slot for its traffic class:
> either block the entire port due to head-of-line blocking, or drop the
> packet and set a bit in the writeback format of the transmit buffer
> descriptor, allowing other packets to be sent.
>
> We obviously choose the second option in the driver, but we do not
> detect the drop condition, so from the perspective of the network stack,
> the packet is sent and no error counter is incremented.
>
> This change checks the writeback of the TX BD when tc-taprio is enabled,
> and increments a specific ethtool statistics counter and a generic
> "tx_dropped" counter in ndo_get_stats64.
>
> Signed-off-by: Po Liu <Po.Liu@....com>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@....com>
Reviewed-by: Claudiu Manoil <claudiu.manoil@....com>
Powered by blists - more mailing lists