From: Jakub Kicinski <kuba@kernel.org>
To: Abhijit Gangurde <abhijit.gangurde@amd.com>
Cc: <jgg@ziepe.ca>, <leon@kernel.org>, <brett.creeley@amd.com>,
<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>, <allen.hubbe@amd.com>,
<nikhil.agarwal@amd.com>, <linux-rdma@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [for-next v3 0/5] ionic: RDMA completion timestamping support
Date: Mon, 8 Jun 2026 14:20:47 -0700 [thread overview]
Message-ID: <20260608142047.6deff079@kernel.org> (raw)
In-Reply-To: <20260606050003.3648306-1-abhijit.gangurde@amd.com>
On Sat, 6 Jun 2026 10:29:58 +0530 Abhijit Gangurde wrote:
> This series adds RDMA completion timestamp support for ionic.
>
> It enables PHC registration for RDMA timestamp capability, exposes a PHC
> state page for safe user-space reads, maps that PHC state through RDMA
> ucontext mmap, and extends the RDMA CQE format to carry completion
> timestamps.
>
> With this, user space can read completion timestamps and convert them to
> wall time with low overhead.
please CC David Woodhouse <dwmw2@infradead.org> on future versions.
Since David is working on uAPI for clocks he may have some thoughts.
prev parent reply other threads:[~2026-06-08 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 4:59 [for-next v3 0/5] ionic: RDMA completion timestamping support Abhijit Gangurde
2026-06-06 4:59 ` [for-next v3 1/5] net: ionic: register PHC for rdma timestamping Abhijit Gangurde
2026-06-06 5:00 ` [for-next v3 2/5] net: ionic: Add PHC state page for user space access Abhijit Gangurde
2026-06-06 5:00 ` [for-next v3 3/5] RDMA/ionic: map PHC state into user space Abhijit Gangurde
2026-06-06 5:00 ` [for-next v3 4/5] RDMA/ionic: add completion timestamp to CQE format Abhijit Gangurde
2026-06-06 5:00 ` [for-next v3 5/5] RDMA/mlx5: move mlx5 clock info to common struct ib_uverbs_clock_info Abhijit Gangurde
2026-06-08 17:30 ` Jason Gunthorpe
2026-06-08 21:20 ` Jakub Kicinski [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=20260608142047.6deff079@kernel.org \
--to=kuba@kernel.org \
--cc=abhijit.gangurde@amd.com \
--cc=allen.hubbe@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=edumazet@google.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikhil.agarwal@amd.com \
--cc=pabeni@redhat.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