From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Salem Sol <salems@nvidia.com>, dev@dpdk.org
Cc: Matan Azrad <matan@nvidia.com>,
Shahaf Shuler <shahafs@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v4 7/7] doc: update sample actions support in mlx5 guide
Date: Tue, 6 Apr 2021 15:45:18 +0100 [thread overview]
Message-ID: <c5486a45-88c6-016e-2719-5a9a8406ce0b@intel.com> (raw)
In-Reply-To: <20210404094910.95413-8-salems@nvidia.com>
On 4/4/2021 10:49 AM, Salem Sol wrote:
> Updates the documentation with the added support for sample actions VXLAN
> and NVGRE encap in E-Switch steering flow.
>
> Signed-off-by: Salem Sol <salems@nvidia.com>
> ---
> doc/guides/nics/mlx5.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
> index 96fce36e3c..378b7202d9 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -376,8 +376,8 @@ Limitations
> encapsulation actions.
> - For NIC Rx flow, supports ``MARK``, ``COUNT``, ``QUEUE``, ``RSS`` in the
> sample actions list.
> - - For E-Switch mirroring flow, supports ``RAW ENCAP``, ``Port ID`` in the
> - sample actions list.
> + - For E-Switch mirroring flow, supports ``RAW ENCAP``, ``Port ID``,
> + ``VXLAN ENCAP``, ``NVGRE ENCAP`` in the sample actions list.
>
> - Modify Field flow:
>
>
Can you please distribute this mlx5 doc patch to the patches that actually adds
the support, very similarly like done with the release notes update patch?
prev parent reply other threads:[~2021-04-06 14:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 9:49 [dpdk-dev] [PATCH v4 0/7] Add support for VXLAN and NVGRE encap as a sample actions Salem Sol
2021-04-04 9:49 ` [dpdk-dev] [PATCH v4 1/7] app/testpmd: store VXLAN/NVGRE encap data globally Salem Sol
2021-04-06 14:54 ` Ferruh Yigit
2021-04-07 11:48 ` [dpdk-dev] [v5 1/6] app/testpmd: prepare storing " Salem Sol
2021-04-07 23:13 ` Ferruh Yigit
2021-04-04 9:49 ` [dpdk-dev] [PATCH v4 2/7] net/mlx5: support VXLAN encap action in sample Salem Sol
2021-04-07 11:48 ` [dpdk-dev] [v5 2/6] " Salem Sol
2021-04-04 9:49 ` [dpdk-dev] [PATCH v4 3/7] net/mlx5: support NVGRE " Salem Sol
2021-04-07 11:49 ` [dpdk-dev] [v5 3/6] " Salem Sol
2021-04-04 9:49 ` [dpdk-dev] [PATCH v4 4/7] app/testpmd: support VXLAN encap for sample action Salem Sol
2021-04-07 11:50 ` [dpdk-dev] [v5 4/6] " Salem Sol
2021-04-04 9:49 ` [dpdk-dev] [PATCH v4 5/7] app/testpmd: support NVGRE " Salem Sol
2021-04-07 11:50 ` [dpdk-dev] [v5 5/6] " Salem Sol
2021-04-04 9:49 ` [dpdk-dev] [PATCH v4 6/7] doc: update sample actions support in testpmd guide Salem Sol
2021-04-07 11:51 ` [dpdk-dev] [v5 6/6] " Salem Sol
2021-04-04 9:49 ` [dpdk-dev] [PATCH v4 7/7] doc: update sample actions support in mlx5 guide Salem Sol
2021-04-06 14:45 ` Ferruh Yigit [this message]
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=c5486a45-88c6-016e-2719-5a9a8406ce0b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=salems@nvidia.com \
--cc=shahafs@nvidia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.