From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>,
Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: RE: [PATCH v1 2/2] net/mlx5: adopt new sample ID
Date: Wed, 22 Mar 2023 09:57:35 +0000 [thread overview]
Message-ID: <DM6PR12MB37531FE1FFE6191DD0A692E0DF869@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230322093815.3736701-3-rongweil@nvidia.com>
> -----Original Message-----
> From: Rongwei Liu <rongweil@nvidia.com>
> Sent: среда, 22 марта 2023 г. 11:38
> To: dev@dpdk.org; Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; NBU-Contact-
> Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>
> Subject: [PATCH v1 2/2] net/mlx5: adopt new sample ID
>
> Extended sample ID is the behavior of the current firmware and this change
> was reverted.
> In Apr GA, the sample ID will be the same as 22.11 DPDK (0-7).
> Now, the sample ID returned by mlx5_devx_cmd_query_parse_samples()
> is still 0-7 and can be used directly by legacy SWS logic.
>
> For HWS, the application should refer to the attributes returned by
> mlx5_devx_cmd_query_match_sample_info to get the sample_dw_data/
> modify_field_id/sample_dw_ok_bit/sample_dw_ok_bit_offset.
>
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
next prev parent reply other threads:[~2023-03-22 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 9:38 [PATCH v1 0/2] fix sample ID backward compatibility Rongwei Liu
2023-03-22 9:38 ` [PATCH v1 1/2] common/mlx5: " Rongwei Liu
2023-03-22 10:00 ` Slava Ovsiienko
2023-03-22 9:38 ` [PATCH v1 2/2] net/mlx5: adopt new sample ID Rongwei Liu
2023-03-22 9:57 ` Slava Ovsiienko [this message]
2023-03-22 12:43 ` [PATCH v1 0/2] fix sample ID backward compatibility 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=DM6PR12MB37531FE1FFE6191DD0A692E0DF869@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rongweil@nvidia.com \
--cc=thomas@monjalon.net \
/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).