All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
	Leon Romanovsky <leonro@nvidia.com>,
	Aharon Landau <aharonl@nvidia.com>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-rdma@vger.kernel.org, Maor Gottlieb <maorg@nvidia.com>,
	netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>
Subject: Re: [PATCH rdma-next 0/2] Provide already supported real-time timestamp
Date: Mon, 21 Jun 2021 20:37:34 -0300	[thread overview]
Message-ID: <20210621233734.GA2363796@nvidia.com> (raw)
In-Reply-To: <cover.1623829775.git.leonro@nvidia.com>

On Wed, Jun 16, 2021 at 10:57:37AM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
> 
> In case device supports only real-time timestamp, the kernel will
> fail to create QP despite rdma-core requested such timestamp type.
> 
> It is because device returns free-running timestamp, and the conversion
> from free-running to real-time is performed in the user space.
> 
> This series fixes it, by returning real-time timestamp.
> 
> Thanks
> 
> Aharon Landau (2):
>   RDMA/mlx5: Refactor get_ts_format functions to simplify code
>   RDMA/mlx5: Support real-time timestamp directly from the device

This looks fine, can you update the shared branch please

Jason

  parent reply	other threads:[~2021-06-21 23:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16  7:57 [PATCH rdma-next 0/2] Provide already supported real-time timestamp Leon Romanovsky
2021-06-16  7:57 ` [PATCH mlx5-next 1/2] RDMA/mlx5: Refactor get_ts_format functions to simplify code Leon Romanovsky
2021-06-16  7:57 ` [PATCH rdma-next 2/2] RDMA/mlx5: Support real-time timestamp directly from the device Leon Romanovsky
2021-06-21 23:37 ` Jason Gunthorpe [this message]
2021-06-22  6:42   ` [PATCH rdma-next 0/2] Provide already supported real-time timestamp Leon Romanovsky
2021-06-22 18:12     ` Jason Gunthorpe

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=20210621233734.GA2363796@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=aharonl@nvidia.com \
    --cc=dledford@redhat.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=maorg@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.