> -----Original Message----- > From: Bing Zhao <[email protected]> > Sent: Thursday, October 22, 2020 17:07 > To: [email protected]; [email protected] > Cc: [email protected]; Ori Kam <[email protected]>; Raslan Darawsheh > <[email protected]> > Subject: [PATCH v2 6/6] net/mlx5: not split hairpin flow in explicit mode > > In the current implementation, the hairpin flow will be split into two flows > implicitly if there is some action that only belongs to the TX part. A TX > device > flow will be inserted by the mlx5 PMD itself. > > In hairpin between two ports, the explicit TX flow mode will be the only one > to > be supported. It is not the appropriate behavior to insert a TX flow into > another device implicitly. The application could create any flow as it likes > and > has full control of the user flows. Hairpin flows will have no difference from > standard flows and the application can decide how to chain RX and TX flows > together. > > Even in the single port hairpin, this explicit TX flow mode could also be > supported. > > When checking if the hairpin needs to be split, just return if the hairpin > queue > is with "tx_explicit" attribute. Then in the following steps for validation > and > translation, the code path will be the same as that for standard flows. > > Signed-off-by: Bing Zhao <[email protected]> Acked-by: Viacheslav Ovsiienko <[email protected]>
> --- > drivers/net/mlx5/mlx5_flow.c | 7 +++++++ > 1 file changed, 7 insertions(+) >
