From: Maayan Kashani <mkashani@nvidia.com>
To: Raslan Darawsheh <rasland@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH 1/2] common/mlx5: read SWS capability bits
Date: Tue, 27 May 2025 08:58:58 +0000 [thread overview]
Message-ID: <PH7PR12MB70184619A31E72598704E8D6B264A@PH7PR12MB7018.namprd12.prod.outlook.com> (raw)
In-Reply-To: <c50dfa76-8d39-4f76-b4d1-aa118e29f267@nvidia.com>
Hi.
Please revert this patch as it is causing a degradation(mark SWS as not supported while it is supported).
Regards,
Maayan Kashani
> -----Original Message-----
> From: Raslan Darawsheh <rasland@nvidia.com>
> Sent: Tuesday, 13 May 2025 9:23
> To: Maayan Kashani <mkashani@nvidia.com>; dev@dpdk.org
> Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Bing Zhao <bingz@nvidia.com>; Ori Kam
> <orika@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>; Matan
> Azrad <matan@nvidia.com>
> Subject: Re: [PATCH 1/2] common/mlx5: read SWS capability bits
>
> Hi,
>
> On 27/04/2025 2:19 PM, Maayan Kashani wrote:
> > SWS will be disabled in future HW generation.
> > Checking SWS capability bits and returning relevant error.
> > if user configuration is not supported, will be added in the follow up
> > commit.
> >
> > Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
> > Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
>
> Series applied to next-net-mlx,
>
> --
> Kindest regards
> Raslan Darawsheh
next prev parent reply other threads:[~2025-05-27 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 11:19 Maayan Kashani
2025-04-27 11:19 ` [PATCH 2/2] net/mlx5: update devarg according to SWS support Maayan Kashani
2025-05-13 6:23 ` [PATCH 1/2] common/mlx5: read SWS capability bits Raslan Darawsheh
2025-05-27 8:58 ` Maayan Kashani [this message]
2025-05-27 9:01 ` 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=PH7PR12MB70184619A31E72598704E8D6B264A@PH7PR12MB7018.namprd12.prod.outlook.com \
--to=mkashani@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--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).