Hi,
From: Itamar Gozlan <igoz...@nvidia.com>
Sent: Sunday, October 27, 2024 6:14 PM
To: Itamar Gozlan; Hamdan Agbariya; NBU-Contact-Thomas Monjalon (EXTERNAL);
Suanming Mou; Dariusz Sosnowski; Slava Ovsiienko; Bing Zhao; Ori Kam; Matan
Azrad; Erez Shitrit
Cc: dev@dpdk.org; sta...@dpdk.org
Subject: [v2] net/mlx5/hws: in NAT64 fix TC to TOS fields mapping
From: Hamdan Igbaria <hamd...@nvidia.com>
In IPv6 to IPv4 scenario when copying the TC field to the
TOS[DSCP:6 bits, ECN: 2 bits] field the mapping of the fields
get set wrongly, since the destination field of TOS is defined as 2
split fields of DSCP and ECN.
In IPv4 to IPv6 we don't have this issue since both the source field of
TOS and destination field of TC defined as 8 bits.
Example to the problematic case of IPv6 to IPv4, TOS to TC mapping:
TC=[abcdefgh], it should be mapped to TOS=[DSCP=abcdef, ECN=gh],
but instead it was mapped as follow TOS=[DSCP=cdefgh, ECN=ab].
Fixes: 06d969a8c5b8 ("net/mlx5/hws: support NAT64 flow action")
Cc: sta...@dpdk.org
Signed-off-by: Hamdan Igbaria <hamd...@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnow...@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
