public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Keith Busch <kbusch@kernel.org>
Cc: Zhiping Zhang <zhipingz@meta.com>, Jason Gunthorpe <jgg@ziepe.ca>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-rdma@vger.kernel.org, linux-pci@vger.kernel.org,
	netdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Yochai Cohen <yochai@nvidia.com>,
	Yishai Hadas <yishaih@nvidia.com>,
	Bjorn Helgaas <helgaas@kernel.org>
Subject: Re: [RFC v2 1/2] vfio: add callback to get tph info for dmabuf
Date: Thu, 16 Apr 2026 18:02:11 +0300	[thread overview]
Message-ID: <20260416150211.GG361495@unreal> (raw)
In-Reply-To: <ad56liSM4zI2SWWp@kbusch-mbp>

On Tue, Apr 14, 2026 at 11:34:14AM -0600, Keith Busch wrote:
> On Thu, Apr 09, 2026 at 03:04:15PM +0300, Leon Romanovsky wrote:
> > Something like that, on top of this proposal:
> 
> ...
>   
> > +struct vfio_region_dma_tph {
> > +	u16 tag;
> > +	u8 ph;
> > +};
> > +
> >  struct vfio_region_dma_range {
> > -	__u64 offset;
> > -	__u64 length;
> > +	union {
> > +		__u64 offset;
> > +		struct vfio_region_dma_tph tph;
> > +	};
> > +	union {
> > +		__u64 length;
> > +		__u64 reserved;
> > +	};
> > +};
> > +
> > +enum {
> > +	VFIO_DMABUF_FLAG_TPH = 1 << 0,
> >  };
> 
> Okay, so you have the hints as a separate action from the dmabuf
> creation. 

I'm not sure I fully understood your point, but in my proposal the entire
operation is done in one pass, with the hints provided as the final entry in
the dma_range array.

Thanks

  reply	other threads:[~2026-04-16 15:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 23:46 [RFC v2 0/2] Retrieve tph from dmabuf for PCIe P2P memory access Zhiping Zhang
2026-03-24 23:46 ` [RFC v2 1/2] vfio: add callback to get tph info for dmabuf Zhiping Zhang
2026-03-25  8:25   ` Leon Romanovsky
2026-03-26 22:41     ` Keith Busch
2026-03-26 22:55       ` Zhiping Zhang
2026-03-31  8:39         ` Leon Romanovsky
2026-03-31  8:37       ` Leon Romanovsky
2026-03-31 13:00         ` Keith Busch
2026-03-31 13:29           ` Leon Romanovsky
2026-03-31 13:35             ` Keith Busch
2026-03-31 14:03               ` Leon Romanovsky
2026-03-31 14:13                 ` Keith Busch
2026-03-31 19:02                   ` Leon Romanovsky
2026-03-31 19:44                     ` Keith Busch
2026-04-09 12:04                       ` Leon Romanovsky
2026-04-13 18:32                         ` Zhiping Zhang
2026-04-13 19:23                           ` Leon Romanovsky
2026-04-14 17:34                         ` Keith Busch
2026-04-16 15:02                           ` Leon Romanovsky [this message]
2026-03-28  2:21   ` fengchengwen
2026-03-31  0:49     ` Zhiping Zhang
2026-03-24 23:46 ` [RFC v2 2/2] RDMA/mlx5: get tph for p2p access when registering dmabuf mr 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=20260416150211.GG361495@unreal \
    --to=leon@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=helgaas@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=kbusch@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 \
    --cc=zhipingz@meta.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