From: Raslan Darawsheh <rasland@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Alex Vesker <valex@nvidia.com>
Subject: RE: [PATCH v2] net/mlx5/hws: fix timestamp format on Tx queue creation
Date: Wed, 9 Nov 2022 09:55:44 +0000 [thread overview]
Message-ID: <BYAPR12MB3078FD6043ED7229DDFC5CF5CF3E9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20221109075753.2449-1-viacheslavo@nvidia.com>
Hi,
> -----Original Message-----
> From: Slava Ovsiienko <viacheslavo@nvidia.com>
> Sent: Wednesday, November 9, 2022 9:58 AM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Alex Vesker <valex@nvidia.com>
> Subject: [PATCH v2] net/mlx5/hws: fix timestamp format on Tx queue
> creation
>
> The NIC since 6DX supports multiple timestamp formats
> in CQEs configured via firmware. If real time timestamp
> format has been configured the correct attributes should
> be specified on queue creation via DevX. These attributes
> setting was missed on steering queue creation and hardware
> steering initialization failed.
>
> Fixes: 3eb748869d2d ("net/mlx5/hws: add send layer")
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
> drivers/net/mlx5/hws/mlx5dr_cmd.c | 4 ++++
> drivers/net/mlx5/hws/mlx5dr_cmd.h | 2 ++
> drivers/net/mlx5/hws/mlx5dr_send.c | 4 ++++
> 3 files changed, 10 insertions(+)
>
> v1:
> - http://patches.dpdk.org/project/dpdk/patch/20221108185650.15489-1-
> viacheslavo@nvidia.com/
> v2:
> - minor style changes
> - removed unnessesary variables
>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-11-09 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 18:56 [PATCH] " Viacheslav Ovsiienko
2022-11-09 7:57 ` [PATCH v2] " Viacheslav Ovsiienko
2022-11-09 9:55 ` 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=BYAPR12MB3078FD6043ED7229DDFC5CF5CF3E9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=valex@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).