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>,
Michael Baum <michaelba@nvidia.com>
Subject: RE: [PATCH v2] net/mlx5: fix MPRQ stride size to accommodate the headroom
Date: Tue, 18 Jul 2023 15:02:16 +0000 [thread overview]
Message-ID: <BYAPR12MB3078A12FB5903F20EC5EB7E3CF38A@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230531190018.948436-1-akozyrev@nvidia.com>
Hi,
> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@nvidia.com>
> Sent: Wednesday, May 31, 2023 10:00 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>; Slava
> Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad <matan@nvidia.com>;
> Michael Baum <michaelba@nvidia.com>
> Subject: [PATCH v2] net/mlx5: fix MPRQ stride size to accommodate the
> headroom
>
> The space for the headroom is reserved at the end of every MPRQ stride for
> the next packet. The Rx burst logic is to copy any overlapping packet data if
> there is an overlap with this reserved headroom space.
> But it is not possible if the headroom size is bigger than the whole stride.
> Adjust the stride size to make sure the stride size is greater than the headroom
> size.
>
> Fixes: 34776af600df ("net/mlx5: fix MPRQ stride devargs adjustment")
>
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
> ---
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2023-07-18 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 18:43 [PATCH] " Alexander Kozyrev
2023-05-31 19:00 ` [PATCH v2] " Alexander Kozyrev
2023-07-18 9:12 ` Slava Ovsiienko
2023-07-18 15:02 ` 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=BYAPR12MB3078A12FB5903F20EC5EB7E3CF38A@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@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).