linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Zhu Yanjun <zyjzyj2000@gmail.com>,
	Leon Romanovsky <leon@kernel.org>,
	Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Jens Axboe <axboe@kernel.dk>,
	Bart Van Assche <bvanassche@acm.org>,
	"kbusch@kernel.org" <kbusch@kernel.org>,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	Amir Goldstein <amir73il@gmail.com>,
	"josef@toxicpanda.com" <josef@toxicpanda.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	"daniel@iogearbox.net" <daniel@iogearbox.net>,
	Christoph Hellwig <hch@lst.de>,
	Dan Williams <dan.j.williams@intel.com>,
	"jack@suse.com" <jack@suse.com>, Jason Gunthorpe <jgg@nvidia.com>,
	Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [LSF/MM/BPF TOPIC] [LSF/MM/BPF ATTEND] : Two stage IOMMU DMA mapping operations
Date: Mon, 4 Mar 2024 03:27:52 +0100	[thread overview]
Message-ID: <22df55f8-cf64-4aa8-8c0b-b556c867b926@linux.dev> (raw)
In-Reply-To: <be75fe5b-9901-425c-8dbb-771dcb084e2e@linux.dev>

在 2024/3/3 17:43, Zhu Yanjun 写道:
> On 27.02.24 12:30, Leon Romanovsky wrote:
>> On Tue, Feb 27, 2024 at 08:17:27AM +0000, Chaitanya Kulkarni wrote:
>>> Hi,
>>
>> <...>
>>
>>> In order to create a good platform for a concrete and meaningful
>>> discussion at LSFMM 24, we plan to post an RFC within the next two 
>>> weeks.
>>
>> The code can be found here 
>> https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/log/?h=dma-split
> 
> Thanks a lot. I will delve into it. An interesting topic.

The commits should be the followings. I am interested in them.

5d8f8f35859c (HEAD -> dma-split, origin/dma-split) cover-letter: Split 
IOMMU DMA mapping operation to two steps
3beffcde0c12 vfio/mlx5: Convert vfio to use DMA link API
acdfef1ccbcb vfio/mlx5: Explicitly store page list
f16314362e66 vfio/mlx5: Rewrite create mkey flow to allow better code reuse
763e753cd6ed vfio/mlx5: Explicitly use number of pages instead of 
allocated length
7f58ebf0cfc4 RDMA/umem: Prevent UMEM ODP creation with SWIOTLB
f1c687fde096 RDMA/core: Separate DMA mapping to caching IOVA and page 
linkage
ffc81619c60d RDMA/umem: Store ODP access mask information in PFN
67038d9e24fd RDMA/umem: Preallocate and cache IOVA for UMEM ODP
ce141bccd409 iommu/dma: Implement link/unlink page callbacks
1dd12d4a44d1 iommu/dma: Prepare map/unmap page functions to receive IOVA
b9714667f54f iommu/dma: Provide an interface to allow preallocate IOVA
21dbfc7fc2f1 dma-mapping: provide callbacks to link/unlink pages to 
specific IOVA
52689a26b87a dma-mapping: provide an interface to allocate IOVA
34f8a8baecaa mm/hmm: let users to tag specific PFNs

Zhu Yanjun

> 
> Zhu Yanjun
> 
>>
>> Thanks
>>
>>>
>>> Required Attendees list :-
>>>
>>> Christoph Hellwig
>>> Jason Gunthorpe
>>> Jens Axboe
>>> Chuck Lever
>>> David Howells
>>> Keith Busch
>>> Bart Van Assche
>>> Damien Le Moal
>>> Martin Petersen
>>>
>>> -ck
>>>
>>> [1]
>>> https://lore.kernel.org/all/169772852492.5232.17148564580779995849.stgit@klimt.1015granger.net
>>> [2] https://lore.kernel.org/linux-iommu/20200708065014.GA5694@lst.de/
>>>
>>>
>>>
> 



  reply	other threads:[~2024-03-04  2:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27  8:17 Chaitanya Kulkarni
2024-02-27 11:30 ` Leon Romanovsky
2024-03-03 16:43   ` Zhu Yanjun
2024-03-04  2:27     ` Zhu Yanjun [this message]
2024-03-05 13:03 ` 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=22df55f8-cf64-4aa8-8c0b-b556c867b926@linux.dev \
    --to=yanjun.zhu@linux.dev \
    --cc=amir73il@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=chaitanyak@nvidia.com \
    --cc=chuck.lever@oracle.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=dan.j.williams@intel.com \
    --cc=daniel@iogearbox.net \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux.dev \
    --cc=jack@suse.com \
    --cc=jgg@nvidia.com \
    --cc=josef@toxicpanda.com \
    --cc=kbusch@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=martin.petersen@oracle.com \
    --cc=zyjzyj2000@gmail.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