DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Alexander Kozyrev <akozyrev@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH] net/mlx5: fix maximum packet headers size for TSO
Date: Tue, 18 Jan 2022 08:33:57 +0000	[thread overview]
Message-ID: <BYAPR12MB30780B84D60888ABD0167E6CCF589@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220113143229.3530296-1-akozyrev@nvidia.com>

Hi,

> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Thursday, January 13, 2022 4:32 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Subject: [PATCH] net/mlx5: fix maximum packet headers size for TSO
> 
> The maximum packet headers size for TSO is calculated as a sum of
> Ethernet, VLAN, IPv6 and TCP headers (plus inner headers).
> The rationale  behind choosing IPv6 and TCP is their headers
> are bigger than IPv4 and UDP respectively, giving us the maximum
> possible headers size. But it is not true for L3 headers.
> IPv4 header size (20 bytes) is smaller than IPv6 header size
> (40 bytes) only in the default case. There are up to 10
> optional header fields called Options in case IHL > 5.
> This means that the maximum size of the IPv4 header is 60 bytes.
> 
> Choosing the wrong maximum packets headers size causes inability
> to transmit multi-segment TSO packets with IPv4 Options present.
> PMD check that it is possible to inline all the packet headers
> and the packet headers size exceeds the expected maximum size.
> The maximum packet headers size was set to 192 bytes before,
> but its value has been reduced during Tx path refactor activity.
> Restore the proper maximum packet headers size for TSO.
> 
> Fixes: 50724e1 ("net/mlx5: update Tx definitions")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2022-01-18  8:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 14:32 Alexander Kozyrev
2022-01-18  8:33 ` 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=BYAPR12MB30780B84D60888ABD0167E6CCF589@BYAPR12MB3078.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=akozyrev@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@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).