On Mon, Oct 16, 2017 at 11:32:39AM +0300, Ori Kam wrote: > Signed-off-by: Ori Kam <[email protected]> > Acked-by: Shahaf Shuler <[email protected]> > --- > doc/guides/nics/mlx5.rst | 5 ++++- > 1 files changed, 4 insertions(+), 1 deletions(-) > > diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst > index d24941a..7da5c87 100644 > --- a/doc/guides/nics/mlx5.rst > +++ b/doc/guides/nics/mlx5.rst > @@ -104,7 +104,8 @@ Limitations > ----------- > > - Inner RSS for VXLAN frames is not supported yet. > -- Port statistics through software counters only. > +- Port statistics through software counters only. Flow statistics are > + supported by hardware counters. > - Hardware checksum RX offloads for VXLAN inner header are not supported yet. > - Forked secondary process not supported. > - Flow pattern without any specific vlan will match for vlan packets as well: > @@ -127,6 +128,8 @@ Limitations > - A multi segment packet must have less than 6 segments in case the Tx burst > function > is set to multi-packet send or Enhanced multi-packet send. Otherwise it > must have > less than 50 segments. > +- Count action for RTE flow is only supported in OFED 4.2. > +- Two identical rules with count action are not supported.
This last line does not bring anything, having two identical rules already create a collision which is not defined by the flow API. In PMD situation is is even worse, as it will match both rules and thus it will duplicate a packet. There is no need to add a limit on an undefined behavior by the API itself. Thanks, PS: when you send a new revision, please use the --thread and --in-reply-to to link it with the previous one. -- Nélio Laranjeiro 6WIND
