From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f65.google.com ([74.125.82.65]:41729 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755117AbeAHS3x (ORCPT ); Mon, 8 Jan 2018 13:29:53 -0500 Received: by mail-wm0-f65.google.com with SMTP id g75so16010784wme.0 for ; Mon, 08 Jan 2018 10:29:52 -0800 (PST) Date: Mon, 8 Jan 2018 11:29:45 -0700 From: Jason Gunthorpe To: Logan Gunthorpe Cc: Christoph Hellwig , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, linux-nvme@lists.infradead.org, linux-rdma@vger.kernel.org, linux-nvdimm@lists.01.org, linux-block@vger.kernel.org, Stephen Bates , Jens Axboe , Keith Busch , Sagi Grimberg , Bjorn Helgaas , Max Gurtovoy , Dan Williams , =?utf-8?B?SsOpcsO0bWU=?= Glisse , Benjamin Herrenschmidt Subject: Re: [PATCH 06/12] IB/core: Add optional PCI P2P flag to rdma_rw_ctx_[init|destroy]() Message-ID: <20180108182945.GG11348@ziepe.ca> References: <20180104190137.7654-1-logang@deltatee.com> <20180104190137.7654-7-logang@deltatee.com> <20180104192225.GS11348@ziepe.ca> <1f8fb3fb-e3dc-94d3-e837-0cd942cf5b87@deltatee.com> <20180104221337.GV11348@ziepe.ca> <3e8391a9-8924-be6d-8c43-162a360d75b6@deltatee.com> <20180105045031.GX11348@ziepe.ca> <20180108145901.GA10743@lst.de> <20180108180917.GF11348@ziepe.ca> <3daea7fe-f64a-36a9-ca80-0cb4d9acf171@deltatee.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <3daea7fe-f64a-36a9-ca80-0cb4d9acf171@deltatee.com> Sender: linux-pci-owner@vger.kernel.org List-ID: On Mon, Jan 08, 2018 at 11:17:38AM -0700, Logan Gunthorpe wrote: > >>If at all it should be in the dma_map* wrappers, but for that we'd need > >>a good identifier. And it still would not solve the whole fake dma > >>ops issue. > > > >Very long term the IOMMUs under the ops will need to care about this, > >so the wrapper is not an optimal place to put it - but I wouldn't > >object if it gets it out of RDMA :) > > Well, creating the extra op doesn't really change anything to the RDMA patch > in this series. Not fundamentally, but it lets us solve the bugs the patch introduces with hfi/etc > The point is, for the time being, we need to track whether we are > doing a P2P or normal mapping using a side channel as we don't have > a good way of tracking it in the SGL at this time. Well, that is disappointing for now, but I'm OK with the flag in the RW interface - as long as we all sort of agree it is not desirable and the SG should self-identify in an ideal someday future world.. Jason