[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210622181231.GG2371267@nvidia.com>
Date: Tue, 22 Jun 2021 15:12:31 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Leon Romanovsky <leon@...nel.org>
Cc: Doug Ledford <dledford@...hat.com>,
Aharon Landau <aharonl@...dia.com>,
Jakub Kicinski <kuba@...nel.org>, linux-rdma@...r.kernel.org,
Maor Gottlieb <maorg@...dia.com>, netdev@...r.kernel.org,
Saeed Mahameed <saeedm@...dia.com>
Subject: Re: [PATCH rdma-next 0/2] Provide already supported real-time
timestamp
On Tue, Jun 22, 2021 at 09:42:07AM +0300, Leon Romanovsky wrote:
> On Mon, Jun 21, 2021 at 08:37:34PM -0300, Jason Gunthorpe wrote:
> > On Wed, Jun 16, 2021 at 10:57:37AM +0300, Leon Romanovsky wrote:
> > > From: Leon Romanovsky <leonro@...dia.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
>
> 9a1ac95a59d0 RDMA/mlx5: Refactor get_ts_format functions to simplify code
>
> Applied, thanks
Done, thanks
Jason
Powered by blists - more mailing lists