From: Zhiping Zhang <zhipingz@meta.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>, <linux-rdma@vger.kernel.org>,
<linux-pci@vger.kernel.org>, <netdev@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
Keith Busch <kbusch@kernel.org>, Yochai Cohen <yochai@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>, Zhiping Zhang <zhipingz@meta.com>
Subject: [RFC 0/2] Retrieve tph from dmabuf for PCIe P2P memory access
Date: Tue, 10 Feb 2026 11:39:53 -0800 [thread overview]
Message-ID: <20260210194014.2147481-1-zhipingz@meta.com> (raw)
Currently, the steering tag can be used for a CPU on the motherboard; the
ACPI check is in place to query and obtain the supported tph settings. Here
we intend to use the tph info to improve RDMA NIC memory access on a vfio-based
accelerator device via PCIe peer-to-peer. When an applicantion register a
RDMA memory region with DMABUF for the RDMA NIC to access the device memory,
the tph associated with the memory region can be retrieved and used to set the
steering tag / process hint (ph). The tph contains additional instructions
or hints to the GPU or accelerator device for advanced memory operations,
such as, read cache selection.
Note this RFC is for the discussion on the direction and is not intended to be
a complete implementation. Once the direction is agreed on, we will work on the
implementation or a real patch set.
Signed-off-by: Zhiping Zhang <zhipingz@meta.com>
[RFC 1/2] Vfio: add callback to get tph info for dmabuf
[RFC 2/2] RMDA MLX5: get tph for p2p access when registering dmabuf
next reply other threads:[~2026-02-10 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 19:39 Zhiping Zhang [this message]
2026-02-10 19:39 ` [RFC 1/2] Vfio: add callback to get tph info for dmabuf Zhiping Zhang
2026-02-27 0:56 ` Keith Busch
2026-03-06 19:27 ` Zhiping Zhang
2026-02-10 19:39 ` [RFC 2/2] RMDA MLX5: get tph for p2p access when registering dmabuf mr Zhiping Zhang
2026-02-27 1:21 ` Keith Busch
2026-03-01 17:55 ` Jason Gunthorpe
2026-03-06 20:48 ` Zhiping Zhang
-- strict thread matches above, loose matches on Subject: below --
2026-02-09 17:53 [RFC 0/2] Retrieve tph from dmabuf for PCIe P2P memory access Zhiping Zhang
2026-02-09 18:13 ` Jason Gunthorpe
2026-02-09 23:28 ` Zhiping Zhang
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=20260210194014.2147481-1-zhipingz@meta.com \
--to=zhipingz@meta.com \
--cc=bhelgaas@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=helgaas@kernel.org \
--cc=jgg@ziepe.ca \
--cc=kbusch@kernel.org \
--cc=leon@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yishaih@nvidia.com \
--cc=yochai@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