From: Li Zhang <lizh@nvidia.com>
To: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Cc: Ori Kam <orika@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Shahaf Shuler <shahafs@nvidia.com>, Shun Hao <shunh@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Raslan Darawsheh <rasland@nvidia.com>,
Roni Bar Yanai <roniba@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v3] doc: document a limitation for a meter with RSS action
Date: Tue, 26 Oct 2021 10:12:06 +0000 [thread overview]
Message-ID: <BN9PR12MB5307C6367467EBD0BDA90B37BF849@BN9PR12MB5307.namprd12.prod.outlook.com> (raw)
In-Reply-To: <3366776.LTxHhVLcFo@thomas>
Thanks Thomas.
Will update the following commit-log in patch v4
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
dv_xmeta_en enabled.
Regards,
Li Zhang
-----Original Message-----
From: Thomas Monjalon <thomas@monjalon.net>
Sent: Tuesday, October 26, 2021 5:51 PM
To: Li Zhang <lizh@nvidia.com>
Cc: Ori Kam <orika@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>; Shahaf Shuler <shahafs@nvidia.com>; Shun Hao <shunh@nvidia.com>; dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>; Roni Bar Yanai <roniba@nvidia.com>; stable@dpdk.org
Subject: Re: [PATCH v3] doc: document a limitation for a meter with RSS action
External email: Use caution opening links or attachments
26/10/2021 11:31, Li Zhang:
> A meter policy with RSS/Queue action is not supported when dv_xmeta_en
> is not zero.
It is still not explaining why.
>
> Fixes: 51ec04d ("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>
> ---
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> - 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 is not zero.
It is still not enclosed like this: ``dv_xmeta_en``
Don't you think "enabled" is better than "not zero"?
next prev parent reply other threads:[~2021-10-26 10:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 2:08 [dpdk-stable] [PATCH] " Li Zhang
2021-10-26 9:24 ` Li Zhang
2021-10-26 9:27 ` [dpdk-stable] [PATCH v2] " Li Zhang
2021-10-26 9:31 ` [dpdk-stable] [PATCH v3] " Li Zhang
2021-10-26 9:51 ` Thomas Monjalon
2021-10-26 10:12 ` Li Zhang [this message]
2021-10-26 10:10 ` [dpdk-stable] [PATCH v4] " Li Zhang
2021-10-26 10:15 ` Thomas Monjalon
2021-10-26 11:54 ` Li Zhang
2021-10-26 11:53 ` [dpdk-stable] [PATCH v5] " Li Zhang
2021-10-26 12:28 ` Thomas Monjalon
2021-10-27 5:41 ` Li Zhang
2021-10-27 5:39 ` [dpdk-stable] [PATCH v6] " Li Zhang
2021-10-27 9:13 ` [dpdk-stable] [PATCH v7] doc: add metering limitation in mlx5 guide Li Zhang
2021-10-31 13:28 ` Raslan Darawsheh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BN9PR12MB5307C6367467EBD0BDA90B37BF849@BN9PR12MB5307.namprd12.prod.outlook.com \
--to=lizh@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=roniba@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=shunh@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).