doc: add metering limitation in mlx5 guide
A meter policy with RSS/Queue action is not supported
when dv_xmeta_en enabled.
When dv_xmeta_en enabled in legacy creating flow,
it will split into two flows
(one set_tag with jump flow and one RSS/queue action flow).
For meter policy as termination table,
it cannot split flow and
cannot support when dv_xmeta_en enabled.
Fixes: 51ec04dc7b
("net/mlx5: connect meter policy to created flows")
Cc: stable@dpdk.org
Signed-off-by: Li Zhang <lizh@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>
This commit is contained in:
parent
a5a0a43bc6
commit
160f0d11bb
@ -435,6 +435,7 @@ Limitations
|
||||
- yellow: QUEUE, RSS, PORT_ID, REPRESENTED_PORT, JUMP, DROP, MARK and SET_TAG.
|
||||
- RED: must be DROP.
|
||||
- Policy actions of RSS for green and yellow should have the same configuration except queues.
|
||||
- Policy with RSS/queue action is not supported when ``dv_xmeta_en`` enabled.
|
||||
- meter profile packet mode is supported.
|
||||
- meter profiles of RFC2697, RFC2698 and RFC4115 are supported.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user