> -----Original Message----- > From: Intel-wired-lan <intel-wired-lan-bounces@xxxxxxxxxx> On Behalf Of Takeru Hayasaka > Sent: Monday, February 12, 2024 7:34 AM > To: Brandeburg, Jesse <jesse.brandeburg@xxxxxxxxx>; Nguyen, Anthony L <anthony.l.nguyen@xxxxxxxxx>; David S. Miller <davem@xxxxxxxxxxxxx>; Eric Dumazet <edumazet@xxxxxxxxxx>; Jakub Kicinski <kuba@xxxxxxxxxx>; Paolo Abeni <pabeni@xxxxxxxxxx>; Jonathan Corbet <corbet@xxxxxxx> > Cc: linux-doc@xxxxxxxxxxxxxxx; vladimir.oltean@xxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; laforge@xxxxxxxxxxxx; Marcin Szycik <marcin.szycik@xxxxxxxxxxxxxxx>; intel-wired-lan@xxxxxxxxxxxxxxxx; Takeru Hayasaka <hayatake396@xxxxxxxxx>; netdev@xxxxxxxxxxxxxxx; mailhol.vincent@xxxxxxxxxx > Subject: [Intel-wired-lan] [PATCH net-next v8 1/2] ethtool: Add GTP RSS hash options to ethtool.h > > This is a patch that enables RSS functionality for GTP packets using ethtool. > >A user can include TEID and make RSS work for GTP-U over IPv4 by doing the >following:`ethtool -N ens3 rx-flow-hash gtpu4 sde` > > In addition to gtpu(4|6), we now support gtpc(4|6),gtpc(4|6)t,gtpu(4|6)e, > gtpu(4|6)u, and gtpu(4|6)d. > > gtpc(4|6): Used for GTP-C in IPv4 and IPv6, where the GTP header format does > not include a TEID. > gtpc(4|6)t: Used for GTP-C in IPv4 and IPv6, with a GTP header format that > includes a TEID. > gtpu(4|6): Used for GTP-U in both IPv4 and IPv6 scenarios. > gtpu(4|6)e: Used for GTP-U with extended headers in both IPv4 and IPv6. > gtpu(4|6)u: Used when the PSC (PDU session container) in the GTP-U extended > header includes Uplink, applicable to both IPv4 and IPv6. > gtpu(4|6)d: Used when the PSC in the GTP-U extended header includes Downlink, > for both IPv4 and IPv6. > > GTP generates a flow that includes an ID called TEID to identify the tunnel. > This tunnel is created for each UE (User Equipment).By performing RSS based on > this flow, it is possible to apply RSS for each communication unit from the UE. > Without this, RSS would only be effective within the range of IP addresses. For > instance, the PGW can only perform RSS within the IP range of the SGW. > Problematic from a load distribution perspective, especially if there's a bias > in the terminals connected to a particular base station.This case can be > solved by using this patch. > > Signed-off-by: Takeru Hayasaka <hayatake396@xxxxxxxxx> > Reviewed-by: Marcin Szycik <marcin.szycik@xxxxxxxxxxxxxxx> > --- > v2->v3: Based on Harald-san's review, I added documentation and comments to > ethtool.h and ice.rst. > v3->v4: Based on Marcin-san's review, I added the missing code for GTPC and > GTPC_TEID, and revised the documentation and comments. > v4->v5: Based on Marcin-san's review, I fixed rename and wrong code regarding > GTPC > v5->v6: Based on Marcin-san's review, Undoing the addition of unnecessary > blank lines.Minor fixes. > v6->v7 Based on Jakub-san's review, Split the patch. > v7->v8: There are no code changes. I've resent the patch, including Marcin-san's > patch, because PatchWork did not interpret the patch correctly.Simon-san told > me. Thanks. > include/uapi/linux/ethtool.h | 48 ++++++++++++++++++++++++++++++++++++ > 1 file changed, 48 insertions(+) > Hi Takeru Hayasaka, Functionality wise its working fine. But the ethtool part (tab complete doesn't show GTP) Please find below logs. [root@os-delivery ~]# ethtool -N eth4 rx-flow-hash ah4 ah6 esp4 esp6 ether sctp4 sctp6 tcp4 tcp6 udp4 udp6 [root@os-delivery ~]# ethtool -N eth4 rx-flow-hash ah4 ah6 esp4 esp6 ether sctp4 sctp6 tcp4 tcp6 udp4 udp6 [root@os-delivery ~]# ethtool -N eth4 rx-flow-hash gtpu6e sdfn [root@os-delivery ~]# ethtool -N eth4 rx-flow-hash gtpu6u sdfn [root@os-delivery ~]# ethtool -N eth4 rx-flow-hash gtpu4u sdfn [root@os-delivery ~]# ethtool -N eth4 rx-flow-hash gtpu4d sdfn [root@os-delivery ~]# ethtool -N eth4 rx-flow-hash gtpu6d sdfn
