From: Raslan Darawsheh <rasland@mellanox.com>
To: Dekel Peled <dekelp@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: update LRO limitation for MLX5
Date: Wed, 6 May 2020 07:50:51 +0000 [thread overview]
Message-ID: <AM0PR05MB6707429566EBE2FCF7ED56A1C2A40@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <b066f7ccbcd068881bf7e6cf4f59eee04e5a64e2.1586688467.git.dekelp@mellanox.com>
Hi,
> -----Original Message-----
> From: Dekel Peled <dekelp@mellanox.com>
> Sent: Sunday, April 12, 2020 1:49 PM
> To: Matan Azrad <matan@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>; Raslan Darawsheh <rasland@mellanox.com>
> Cc: dev@dpdk.org
> Subject: [PATCH] doc: update LRO limitation for MLX5
>
> MLX5 PMD limitation regarding use of LRO is updated.
>
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> Acked-by: Matan Azrad <matan@mellanox.com>
> ---
> doc/guides/nics/mlx5.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
> index e13c07d..ff09e51 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -256,6 +256,9 @@ Limitations
> TCP header (122B).
> - Rx queue with LRO offload enabled, receiving a non-LRO packet, can
> forward
> it with size limited to max LRO size, not to max RX packet length.
> + - LRO can be used with outer header of TCP packets of the standard
> format:
> + eth (with or without vlan) / ipv4 or ipv6 / tcp / payload
> + Other TCP packets (e.g. with MPLS label) received on Rx queue with LRO
> enabled, will be received with bad checksum.
>
> Statistics
> ----------
> --
> 1.8.3.1
Fixed warning when building the docs.
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-05-06 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 10:48 Dekel Peled
2020-05-06 7: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=AM0PR05MB6707429566EBE2FCF7ED56A1C2A40@AM0PR05MB6707.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dekelp@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).