From: Jason Gunthorpe <jgg@nvidia.com>
To: 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>,
Leon Romanovsky <leonro@nvidia.com>
Subject: Re: [LSF/MM/BPF TOPIC] [LSF/MM/BPF ATTEND] : Two stage IOMMU DMA mapping operations
Date: Tue, 5 Mar 2024 09:03:31 -0400 [thread overview]
Message-ID: <20240305130331.GA3662014@nvidia.com> (raw)
In-Reply-To: <97f385db-42c9-4c04-8fba-9b1ba8ffc525@nvidia.com>
On Tue, Feb 27, 2024 at 08:17:27AM +0000, Chaitanya Kulkarni wrote:
> Hi,
>
> * Problem Statement :-
> -------------------------------------------------------------------------
> The existing IOMMU DMA mapping operation is performed in two steps at the
> same time (one-shot):
> 1. Allocates IOVA space.
> 2. Actually maps DMA pages to that space.
> For example, map scatter-gather list:
For clarity, this has come out of last years topic on the "physr" - we
agreed to a general direction where instead of adding a parallel DMA
API surface for a new scatterlist alternative we'd improve the DMA API
so callers can efficiently bring their own data structure.
https://lore.kernel.org/linux-rdma/Y8v+qVZ8OmodOCQ9@nvidia.com/
Jason
prev parent reply other threads:[~2024-03-05 13:03 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
2024-03-05 13:03 ` Jason Gunthorpe [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=20240305130331.GA3662014@nvidia.com \
--to=jgg@nvidia.com \
--cc=amir73il@gmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=chaitanyak@nvidia.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=josef@toxicpanda.com \
--cc=kbusch@kernel.org \
--cc=leonro@nvidia.com \
--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 \
/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