From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: 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: [PATCH rdma-next 0/2] Provide already supported real-time timestamp
Date: Wed, 16 Jun 2021 10:57:37 +0300 [thread overview]
Message-ID: <cover.1623829775.git.leonro@nvidia.com> (raw)
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
drivers/infiniband/hw/mlx5/cq.c | 6 +-
drivers/infiniband/hw/mlx5/main.c | 6 ++
drivers/infiniband/hw/mlx5/mlx5_ib.h | 7 ++
drivers/infiniband/hw/mlx5/qp.c | 102 ++++++++++--------
.../net/ethernet/mellanox/mlx5/core/en_main.c | 8 +-
.../ethernet/mellanox/mlx5/core/lib/clock.h | 10 +-
include/linux/mlx5/mlx5_ifc.h | 36 ++-----
include/linux/mlx5/qp.h | 4 +-
include/uapi/rdma/mlx5-abi.h | 2 +
9 files changed, 94 insertions(+), 87 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-16 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 7:57 Leon Romanovsky [this message]
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 ` [PATCH rdma-next 0/2] Provide already supported real-time timestamp Jason Gunthorpe
2021-06-22 6:42 ` 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=cover.1623829775.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=aharonl@nvidia.com \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=kuba@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.