patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: "christian.ehrhardt@canonical.com" <christian.ehrhardt@canonical.com>
Subject: Re: [dpdk-stable] [PATCH 20.11] net/mlx5: fix receiving queue timestamp format
Date: Sun, 20 Jun 2021 14:10:26 +0000	[thread overview]
Message-ID: <DM4PR12MB537383CDA7B2DACD0589EB8BA10B9@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210616165552.13014-1-viacheslavo@nvidia.com>

Hi Slava,

Thanks for the patch, we need a upstream tag to indicate original patch commit ID in upstream main branch.
Please send a new version once ready, thanks.

Best Regards,
Xueming

> -----Original Message-----
> From: Slava Ovsiienko <viacheslavo@nvidia.com>
> Sent: Thursday, June 17, 2021 12:56 AM
> To: stable@dpdk.org
> Cc: christian.ehrhardt@canonical.com; Xueming(Steven) Li <xuemingl@nvidia.com>
> Subject: [PATCH 20.11] net/mlx5: fix receiving queue timestamp format
> 
> The timestamp format was not configured correctly for the receiving queues created via DevX calls. It caused non-UTC timestamps in
> CQEs  for real time configurations.
> 
> Fixes: d61381ad46d0 ("net/mlx5: support timestamp format")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
>  drivers/net/mlx5/mlx5_devx.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/net/mlx5/mlx5_devx.c b/drivers/net/mlx5/mlx5_devx.c index 377362e321..0256307b1c 100644
> --- a/drivers/net/mlx5/mlx5_devx.c
> +++ b/drivers/net/mlx5/mlx5_devx.c
> @@ -339,6 +339,7 @@ mlx5_rxq_create_devx_rq_resources(struct rte_eth_dev *dev, uint16_t idx)
>  	rq_attr.mem_rq_type = MLX5_RQC_MEM_RQ_TYPE_MEMORY_RQ_INLINE;
>  	rq_attr.flush_in_error_en = 1;
>  	mlx5_devx_create_rq_attr_fill(rxq_data, cqn, &rq_attr);
> +	rq_attr.ts_format = mlx5_ts_format_conv(priv->sh->rq_ts_format);
>  	/* Fill WQ attributes for this RQ. */
>  	if (mlx5_rxq_mprq_enabled(rxq_data)) {
>  		rq_attr.wq_attr.wq_type = MLX5_WQ_TYPE_CYCLIC_STRIDING_RQ;
> --
> 2.18.1


  reply	other threads:[~2021-06-20 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 16:55 Viacheslav Ovsiienko
2021-06-20 14:10 ` Xueming(Steven) Li [this message]
2021-06-25 14:10 Viacheslav Ovsiienko

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=DM4PR12MB537383CDA7B2DACD0589EB8BA10B9@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=christian.ehrhardt@canonical.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).