From: Raslan Darawsheh <rasland@mellanox.com>
To: Raslan Darawsheh <rasland@mellanox.com>,
Matan Azrad <matan@mellanox.com>,
Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc/mlx5: remove limitation for TSO over VM
Date: Thu, 14 May 2020 09:35:02 +0000 [thread overview]
Message-ID: <AM0PR05MB67072799198BEFFF0B0F8050C2BC0@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20200513110031.16353-1-rasland@mellanox.com>
Hi,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Raslan Darawsheh
> Sent: Wednesday, May 13, 2020 2:01 PM
> To: Matan Azrad <matan@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] doc/mlx5: remove limitation for TSO over VM
>
> removing the current limnitation for TSO over VM
> due to the fact that MLX5 currently support it.
>
> Signed-off-by: Raslan Darawsheh <rasland@mellanox.com>
> ---
> doc/guides/nics/mlx5.rst | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
> index a8c27b485..6a4f582f6 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -163,8 +163,6 @@ Limitations
> - Flows with a VXLAN Network Identifier equal (or ends to be equal)
> to 0 are not supported.
>
> -- VXLAN TSO and checksum offloads are not supported on VM.
> -
> - L3 VXLAN and VXLAN-GPE tunnels cannot be supported together with
> MPLSoGRE and MPLSoUDP.
>
> - Match on Geneve header supports the following fields only:
> --
> 2.26.0
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-05-14 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 11:00 Raslan Darawsheh
2020-05-14 5:54 ` Asaf Penso
2020-05-14 9:35 ` 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=AM0PR05MB67072799198BEFFF0B0F8050C2BC0@AM0PR05MB6707.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=viacheslavo@mellanox.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).