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>,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>
Subject: Re: [PATCH v3] net/mlx5: fix RSS hash for non-RSS CQE zipping
Date: Sun, 19 Jan 2025 11:47:46 +0000 [thread overview]
Message-ID: <DM4PR12MB8452CBAA7E39A4D6A4B081E1CFE42@DM4PR12MB8452.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20241130003925.2228586-1-akozyrev@nvidia.com>
Hi,
From: Alexander Kozyrev <akozyrev@nvidia.com>
Sent: Saturday, November 30, 2024 2:39 AM
To: dev@dpdk.org
Cc: stable@dpdk.org; Raslan Darawsheh; Slava Ovsiienko; Matan Azrad; Dariusz Sosnowski; Bing Zhao; Suanming Mou
Subject: [PATCH v3] net/mlx5: fix RSS hash for non-RSS CQE zipping
Take the RSS hash value from the title packet
before it gets overwritten by the decompression routine.
Set the RSS hash flag in the packet mbuf if RSS is enabled
in case of non-RSS CQE zipping format.
Fixes: 54c2d46 ("net/mlx5: support flow tag and packet header miniCQEs")
Cc: stable@dpdk.org
Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
Sending reply to the correct Patch version,
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2025-01-19 11:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 13:32 [PATCH] " Alexander Kozyrev
2024-11-21 14:56 ` Dariusz Sosnowski
2024-11-29 20:44 ` [PATCH v2] " Alexander Kozyrev
2024-11-30 0:39 ` [PATCH v3] " Alexander Kozyrev
2024-12-02 14:27 ` Dariusz Sosnowski
2025-01-19 11:47 ` Raslan Darawsheh [this message]
2025-01-19 13:09 ` Alexander Kozyrev
2025-01-19 11:46 ` [PATCH v2] " Raslan Darawsheh
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=DM4PR12MB8452CBAA7E39A4D6A4B081E1CFE42@DM4PR12MB8452.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=akozyrev@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--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).