[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM9PR04MB83979D5442EC78B8BA67B04B96B19@AM9PR04MB8397.eurprd04.prod.outlook.com>
Date: Thu, 7 Oct 2021 18:14:35 +0000
From: Claudiu Manoil <claudiu.manoil@....com>
To: Ioana Ciornei <ioana.ciornei@....com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Vladimir Oltean <vladimir.oltean@....com>
Subject: RE: [PATCH net-next v2 2/2] net: enetc: add support for software TSO
> -----Original Message-----
> From: Ioana Ciornei <ioana.ciornei@....com>
> Sent: Thursday, October 7, 2021 6:31 PM
[...]
> Subject: [PATCH net-next v2 2/2] net: enetc: add support for software TSO
>
> This patch adds support for driver level TSO in the enetc driver using
> the TSO API.
>
> Beside using the usual tso_build_hdr(), tso_build_data() this specific
> implementation also has to compute the checksum, both IP and L4, for
> each resulted segment. This is because the ENETC controller does not
> support Tx checksum offload which is needed in order to take advantage
> of TSO.
>
> With the workaround for the ENETC MDIO erratum in place the Tx path of
> the driver is forced to lock/unlock for each skb sent. This is why, even
> though we are computing the checksum by hand we see the following
> improvement in TCP termination on the LS1028A SoC, on a single A72 core
> running at 1.3GHz:
>
> before: 1.63 Gbits/sec
> after: 2.34 Gbits/sec
>
> Signed-off-by: Ioana Ciornei <ioana.ciornei@....com>
> ---
> Changes in v2:
> - add support for TSO over IPv6 (NETIF_F_TSO6 and csum compute)
>
Reviewed-by: Claudiu Manoil <claudiu.manoil@....com>
Powered by blists - more mailing lists