From: Raslan Darawsheh <rasland@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
Dmitry Kozlyuk <dkozlyuk@nvidia.com>,
Raja Zidane <rzidane@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] net/mlx5: fix condition to avoid Tx failure
Date: Thu, 18 Aug 2022 11:08:16 +0000 [thread overview]
Message-ID: <BYAPR12MB30786303D35E8168B5E0FAFFCF6D9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220817141433.7654-1-viacheslavo@nvidia.com>
Hi,
> -----Original Message-----
> From: Slava Ovsiienko <viacheslavo@nvidia.com>
> Sent: Wednesday, August 17, 2022 5:15 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Dmitry Kozlyuk <dkozlyuk@nvidia.com>; Raja Zidane
> <rzidane@nvidia.com>; stable@dpdk.org
> Subject: [PATCH] net/mlx5: fix condition to avoid Tx failure
>
> From: Raja Zidane <rzidane@nvidia.com>
>
> If hardware descriptor (WQE) length exceeds one the HW can handle,
> the Tx queue failure occurs. PMD does the length check but there was
> a bug - the length limit was expressed in 16B units (WQEBB segments),
> while the calculated WQE length and limit were in 64B units (WQEBBs).
> Fix the condition to avoid subsequent Tx queue failure.
>
> Fixes: 18a1c20 ("net/mlx5: implement Tx burst template")
> Cc: stable@dpdk.org
>
> Signed-off-by: Raja Zidane <rzidane@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-08-18 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 14:14 Viacheslav Ovsiienko
2022-08-18 11:08 ` 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=BYAPR12MB30786303D35E8168B5E0FAFFCF6D9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=dkozlyuk@nvidia.com \
--cc=matan@nvidia.com \
--cc=rzidane@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).