Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3152664imu; Mon, 19 Nov 2018 11:27:03 -0800 (PST) X-Google-Smtp-Source: AJdET5ekUVOgJo9T5UhBg2QJSM1/sFw5qec5w6SN6IjAT42RwYHJ0cgrStQdS+x/QNRDM7yn4+dd X-Received: by 2002:a17:902:110a:: with SMTP id d10-v6mr23905106pla.85.1542655623598; Mon, 19 Nov 2018 11:27:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542655623; cv=none; d=google.com; s=arc-20160816; b=s5vsxcJ3jxbZtmz+kdy6/cP89OIolhIcKTIb50+g9uXxMfHUHJJLfk1M8fTO+OBNSB F1ykAb4jERCOlf3vc1NOrshBY16rW9BfebhUmz+fZaFuji100tmIZ3nFVPHrtxKP6txw gF69l4072fKMY5fB75ZnoHeOM4EwRY3+mQqOnpmdBkpDLWnR5E7qFLgsXUN5aCuZcfM8 JHwbESdpx/4fK5VGFHr0CGv1YOQJoipVa8iMKoWx3ICRM/P7x3+ElGXpGHsDbEu/g3ic pAkINObpJwLzQ2xfx0L227ecTAzUTrSeKVrC3m10XCkMWo++I7qE152zaF8J8TfOnSW4 4FDw== 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; bh=3FW2eRJhnaGbSBRJoEvac6nYk+t3QAWdLVrseO0vL6E=; b=n7qnB27wII9dAkzG3AKN8tQ2JFPD8eBRB3DGy0tnlFxsH7u/JvQv5WtXawWDDv73V1 eG360dOfZycrHxWW7D1FKO8+oPAlRb+lJM2Zk0qi9LWKwAW66JESxyeyOyt2kcR2XBOz 5l8geFokCqzICQwGl3wn5Euyraup4b2C5Ke5EqhULgudhd8kRX2Z1cPQs9CY/cogvhmT mcVpp8gyo7D+TLvFhNT0ZnZQ/m0xfqoJCM41Bl76dbjJtZ/Pf1ZUZ+GIbzK9EtFO8fWU fo7RZPMkRb1k5f4smsTuZkeAPLqIJuEJG8b9jaVJRgsjKAr4ECRtzRGj0TrKv81rGC+R g7sA== 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 20si38468656pgg.271.2018.11.19.11.26.48; Mon, 19 Nov 2018 11:27:03 -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 S1730264AbeKTFuX (ORCPT + 99 others); Tue, 20 Nov 2018 00:50:23 -0500 Received: from mx1.redhat.com ([209.132.183.28]:34010 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725987AbeKTFuX (ORCPT ); Tue, 20 Nov 2018 00:50:23 -0500 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 92D1C305C3B8; Mon, 19 Nov 2018 19:25:20 +0000 (UTC) Received: from redhat.com (ovpn-124-1.rdu2.redhat.com [10.10.124.1]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1008D84F9; Mon, 19 Nov 2018 19:25:14 +0000 (UTC) Date: Mon, 19 Nov 2018 14:25:13 -0500 From: Jerome Glisse To: Christopher Lameter Cc: Jason Gunthorpe , Leon Romanovsky , Kenneth Lee , Tim Sell , linux-doc@vger.kernel.org, Alexander Shishkin , Zaibo Xu , zhangfei.gao@foxmail.com, linuxarm@huawei.com, haojian.zhuang@linaro.org, Hao Fang , Gavin Schenk , RDMA mailing list , Zhou Wang , Doug Ledford , Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= , David Kershner , Kenneth Lee , Johan Hovold , Cyrille Pitchen , Sagar Dharia , Jens Axboe , guodong.xu@linaro.org, linux-netdev , Randy Dunlap , linux-kernel@vger.kernel.org, Vinod Koul , linux-crypto@vger.kernel.org, Philippe Ombredanne , Sanyog Kale , "David S. Miller" , linux-accelerators@lists.ozlabs.org Subject: Re: [RFCv3 PATCH 1/6] uacce: Add documents for WarpDrive/uacce Message-ID: <20181119192512.GD4593@redhat.com> References: <20181114160017.GI3759@mtr-leonro.mtl.com> <20181115085109.GD157308@Turing-Arch-b> <20181115145455.GN3759@mtr-leonro.mtl.com> <20181119091405.GE157308@Turing-Arch-b> <20181119091910.GF157308@Turing-Arch-b> <20181119104801.GF8268@mtr-leonro.mtl.com> <20181119164853.GA4593@redhat.com> <20181119182752.GA4890@ziepe.ca> <20181119184215.GB4593@redhat.com> <010001672d69716a-743e5098-eb2f-41ca-bf98-6e17eaaba00f-000000@email.amazonses.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <010001672d69716a-743e5098-eb2f-41ca-bf98-6e17eaaba00f-000000@email.amazonses.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.45]); Mon, 19 Nov 2018 19:25:21 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 19, 2018 at 07:19:04PM +0000, Christopher Lameter wrote: > On Mon, 19 Nov 2018, Jerome Glisse wrote: > > > > IIRC this is solved in IB by automatically calling > > > madvise(MADV_DONTFORK) before creating the MR. > > > > > > MADV_DONTFORK > > > .. This is useful to prevent copy-on-write semantics from changing the > > > physical location of a page if the parent writes to it after a > > > fork(2) .. > > > > This would work around the issue but this is not transparent ie > > range marked with DONTFORK no longer behave as expected from the > > application point of view. > > Why would anyone expect a range registered via MR behave as normal? Device > I/O is going on into that range. Memory is already special. > > > > Also it relies on userspace doing the right thing (which is not > > something i usualy trust :)). > > This has been established practice for 15 or so years in a couple of use > cases. Again user space already has to be doing special things in order to > handle RDMA is that area. Yes RDMA as an existing historical track record and thus people should now be aware of its limitation. What i am fighting against is new addition to kernel that pretend to do SVA (share virtual address) while their hardware is not realy doing SVA. SVA with IOMMU and ATS/PASID is fine, SVA in software with device driver that abide to mmu notifier is fine. Anything else is not. So i am just worrying about new user and making sure they under- stand what is happening and not sell to their user something false. Cheers, J?r?me