From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Subject: Re: [PATCH v8 13/14] IB/core: use MAP_DIRECT to fix / enable RDMA to DAX mappings Date: Wed, 11 Oct 2017 09:01:25 -0700 Message-ID: References: <150764693502.16882.15848797003793552156.stgit@dwillia2-desk3.amr.corp.intel.com> <150764701194.16882.9682569707416653741.stgit@dwillia2-desk3.amr.corp.intel.com> <20171011115410.GF30803@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20171011115410.GF30803-zLv9SwRftAIdnm+yROfE0A@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Joerg Roedel Cc: "J. Bruce Fields" , Doug Ledford , Jan Kara , "Darrick J. Wong" , linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Linux API , "linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org" , Dave Chinner , iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, Hal Rosenstock , linux-xfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-mm , Jeff Moyer , Jeff Layton , Ross Zwisler , linux-fsdevel , Sean Hefty , David Woodhouse , Christoph Hellwig List-Id: linux-api@vger.kernel.org On Wed, Oct 11, 2017 at 4:54 AM, Joerg Roedel wrote: > On Tue, Oct 10, 2017 at 07:50:12AM -0700, Dan Williams wrote: >> +static void ib_umem_lease_break(void *__umem) >> +{ >> + struct ib_umem *umem = umem; >> + struct ib_device *idev = umem->context->device; >> + struct device *dev = idev->dma_device; >> + struct scatterlist *sgl = umem->sg_head.sgl; >> + >> + iommu_unmap(umem->iommu, sg_dma_address(sgl) & PAGE_MASK, >> + iommu_sg_num_pages(dev, sgl, umem->npages)); >> +} > > This looks like an invitation to break your code by random iommu-driver > changes. There is no guarantee that an iommu-backed dma-api > implemenation will map exactly iommu_sg_num_pages() pages for a given > sg-list. In other words, you are mixing the use of the IOMMU-API and the > DMA-API in an incompatible way that only works because you know the > internals of the iommu-drivers. > > I've seen in another patch that your changes strictly require an IOMMU, > so you what you should do instead is to switch from the DMA-API to the > IOMMU-API and do the address-space management yourself. > Ok, I'll switch over completely to the iommu api for this. It will also address Robin's concern.