Received: by 10.223.185.116 with SMTP id b49csp7921757wrg; Thu, 1 Mar 2018 13:37:18 -0800 (PST) X-Google-Smtp-Source: AG47ELv4zyACskkeujQ0ji9puDB0tWRUhFn3iL6PPgVeYjcaP6eB3+s0xL93kTR4P2BBcEwrnpwq X-Received: by 10.98.65.72 with SMTP id o69mr3311986pfa.97.1519940238496; Thu, 01 Mar 2018 13:37:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519940238; cv=none; d=google.com; s=arc-20160816; b=BjRLi5oYTl8f3tNUS7vh9H09KojuaS3pfExz2wTWSU4NtV3nToulflKuaTbXU5XiIz DnJikkA8XK5MxjWoxo1wifj0sornHVqiptPr1+jA1t5DeLrysuOv0388gK68vWCDHpOs IRaTbd4UL4NcRsw4RXV1ChfJOq0WS3hSbisJL9qg2yOO0Bz6aHEZyVCN/M4kWSLBUiFs nmy7GuZUmMd/deLYDEbA7qFWZHK3gO8KIztKdDdjadb5OvJ74YDETtK4FMZPJ4HdQzfb glf2b7ux8mpPHBkghPdkBFjtr0TIGIyyIPTQ3K6TjK6ZfDBXqro+RA5dxB1QgDdd9Mtx zm9g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=PTELjd3wWpTJtPH+A0DaE6OpgsFCu4CEDSPYEfpxEDo=; b=ukuVAZetPLizNdSQ0ZL5iA6/pF5ySb9yMrUs/kqkuSt4vqhjSftsU4BU36kHBUcPkk yn/ypALZgyv1YfxvY5L9/uLQpMXmHZ7niZWMNumkUylorFT5qqeSBV3XSzbHWLawQUct AWPCAHH4MH66x5WfZnzoa834xDqJoCBFWXy4Liawht/BOnSoJUqbdYWHuBoAAcf6P8I6 sXa+v8hj33k/wiExG8gE/bYE2qr5Ux5f8GwVMuGqmcfs6dHXM2pPyL8su8YWoUXBonnB ELInXD/j6zR2MOUpQk0g7ChqBHrpTZtxz7MT1XnBYNOJ6Lqf682qNbwQLDkCJ49B3Eua sxLQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 65-v6si3616736pla.409.2018.03.01.13.37.03; Thu, 01 Mar 2018 13:37:18 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1162249AbeCAVfx (ORCPT + 99 others); Thu, 1 Mar 2018 16:35:53 -0500 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:45198 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1162225AbeCAVfi (ORCPT ); Thu, 1 Mar 2018 16:35:38 -0500 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id ACF4E814DF58; Thu, 1 Mar 2018 21:35:37 +0000 (UTC) Received: from redhat.com (ovpn-124-164.rdu2.redhat.com [10.10.124.164]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6C297213AEF8; Thu, 1 Mar 2018 21:35:35 +0000 (UTC) Date: Thu, 1 Mar 2018 16:35:33 -0500 From: Jerome Glisse To: Stephen Bates Cc: Alex Williamson , Bjorn Helgaas , Logan Gunthorpe , "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" , Christoph Hellwig , Jens Axboe , Keith Busch , Sagi Grimberg , Bjorn Helgaas , Jason Gunthorpe , Max Gurtovoy , Dan Williams , Benjamin Herrenschmidt Subject: Re: [PATCH v2 04/10] PCI/P2PDMA: Clear ACS P2P flags for all devices behind switches Message-ID: <20180301213533.GE6742@redhat.com> References: <20180228234006.21093-1-logang@deltatee.com> <20180228234006.21093-5-logang@deltatee.com> <20180301180257.GH13722@bhelgaas-glaptop.roam.corp.google.com> <0D05579B-789C-4A19-B3A2-C1A630BE31C0@raithlin.com> <20180301142155.5966c4c0@w520.home> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Thu, 01 Mar 2018 21:35:38 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]); Thu, 01 Mar 2018 21:35:38 +0000 (UTC) for IP:'10.11.54.6' DOMAIN:'int-mx06.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'jglisse@redhat.com' RCPT:'' Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 01, 2018 at 09:32:20PM +0000, Stephen Bates wrote: > > your kernel provider needs to decide whether they favor device assignment or p2p > > Thanks Alex! The hardware requirements for P2P (switch, high performance EPs) are such that we really only expect CONFIG_P2P_DMA to be enabled in specific instances and in those instances the users have made a decision to favor P2P over IOMMU isolation. Or they have setup their PCIe topology in a way that gives them IOMMU isolation where they want it and P2P where they want it. > > Note that they are usecase for P2P where IOMMU isolation matter and the traffic through root complex isn't see as an issue. For instance for GPU the idea is that you want to allow the RDMA device to directly read or write from GPU memory to avoid having to migrate memory to system memory. This isn't so much for performance than for ease of use. Cheers, J?r?me