From: Raslan Darawsheh <rasland@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Slava Ovsiienko" <viacheslavo@nvidia.com>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix tunnel offload rules validation on VF representor.
Date: Thu, 17 Dec 2020 09:50:59 +0000 [thread overview]
Message-ID: <DM6PR12MB274812905B1C24F8577824DFCFC40@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201211144614.24204-1-getelson@nvidia.com>
Hi,
> -----Original Message-----
> From: Gregory Etelson <getelson@nvidia.com>
> Sent: Friday, December 11, 2020 4:46 PM
> To: dev@dpdk.org
> Cc: Gregory Etelson <getelson@nvidia.com>; Matan Azrad
> <matan@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>;
> stable@dpdk.org; Slava Ovsiienko <viacheslavo@nvidia.com>; Shahaf Shuler
> <shahafs@nvidia.com>
> Subject: [PATCH] net/mlx5: fix tunnel offload rules validation on VF
> representor.
>
Changed commit log, fixed wrong headline format and removed offload extra word to keep title shorter.
> MLX5 PMD implicitly adds vxlan_decap flow action to tunnel offload
> match type rules. However, VXLAN decap action on VF representors is
> not supported on MLX5 PMD hardware.
>
> The patch rejects attempt to create tunnel offload flow rules on VF
> representor.
>
> Refer: commit 9c4971e5231d ("net/mlx5: update VLAN and encap actions
> validation")
>
> Fixes: 4ec6360de37d ("net/mlx5: implement tunnel offload")
>
> cc: stable@dpdk.org
>
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-12-17 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 14:46 Gregory Etelson
2020-12-17 9:50 ` Raslan Darawsheh [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=DM6PR12MB274812905B1C24F8577824DFCFC40@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=stable@dpdk.org \
--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).