Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp587006imj; Thu, 7 Feb 2019 08:49:24 -0800 (PST) X-Google-Smtp-Source: AHgI3IaZ7ZpdWTnS0HgJx2ezlhZh4TjznNWLbHYwB1zUFEODtfJxHdWNcxriydUBFGqQMKkynOH0 X-Received: by 2002:a63:3541:: with SMTP id c62mr11583038pga.191.1549558164453; Thu, 07 Feb 2019 08:49:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549558164; cv=none; d=google.com; s=arc-20160816; b=jEKMvR5kCqafUEyEUdw+atqZ1Ro7SJ9pni2Kk9Dq6zppS9IIB3F8eAPjgBjLUYqFrX K1zSVyvG48IoyMhdf0ufMbx7P7BSbdU/syJjaJaqmHYtNKYTja4dzKTvlL4KUkkUnwus 6Iq9Z60OOMYXm8a92AtLi8X7pZdp3tDqSKREKsz1zknxcSiCMDmvvGnOrn7VZjDXPQJl RE5YDm17JYWT32EoGbLrLne3/tLVkPLQwtXEvayKx1cLm0Va1pBjuDS0q2pdMqdi3y8j RQwalHQ/UgfBBs2eAZOTw1622m1Z4ftov8HiPjHvjLruj8/7N1eUJMsZpE20WJIYXtKU oVZA== 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-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=cNwE52CAtIF+radn0yGPCF9d34z+lppjpIAOK4UeaOE=; b=J8AfKiDSGw+3WJNxVDtGL5/f80Tjbicy4ZI+tVAucnKPiFkPED4CIUehfjRBUd5GTR UatBdbjlwfcdbnXwCV8O89+7SA45UHHG+hsd5NsVAc5pofd3xszDrD/0fnQnU3D/Njg1 oXIE/eddBSU3QSZwZapqzPPFQ8qyy0+DMafdhiErxqEztMI95hpNldfzLcAC+0RoL6qU thsVTom9uPXFKtqU9J34C2IwEq4AQFh2ERpiSwAIh3Iyx2tRLWreX7azsXTnaAtYjUQ7 MKVvoYYTF6AVHV4zA159KMwrIPVhIDtEQy0kaqVlR17JOI23fQJEt+0T47tHFaTply7Q XiOw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v7si4963201pga.15.2019.02.07.08.49.08; Thu, 07 Feb 2019 08:49:24 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726905AbfBGQsk (ORCPT + 99 others); Thu, 7 Feb 2019 11:48:40 -0500 Received: from mx2.suse.de ([195.135.220.15]:39452 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726196AbfBGQsk (ORCPT ); Thu, 7 Feb 2019 11:48:40 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 73FC8B017; Thu, 7 Feb 2019 16:48:38 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id CFDD71E3DB5; Thu, 7 Feb 2019 17:48:36 +0100 (CET) Date: Thu, 7 Feb 2019 17:48:36 +0100 From: Jan Kara To: Doug Ledford Cc: Matthew Wilcox , Christopher Lameter , Jason Gunthorpe , Jan Kara , Ira Weiny , lsf-pc@lists.linux-foundation.org, linux-rdma@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, John Hubbard , Jerome Glisse , Dan Williams , Dave Chinner , Michal Hocko Subject: Re: [LSF/MM TOPIC] Discuss least bad options for resolving longterm-GUP usage by RDMA Message-ID: <20190207164836.GL3597@quack2.suse.cz> References: <20190205175059.GB21617@iweiny-DESK2.sc.intel.com> <20190206095000.GA12006@quack2.suse.cz> <20190206173114.GB12227@ziepe.ca> <20190206175233.GN21860@bombadil.infradead.org> <47820c4d696aee41225854071ec73373a273fd4a.camel@redhat.com> <01000168c43d594c-7979fcf8-b9c1-4bda-b29a-500efe001d66-000000@email.amazonses.com> <20190206194055.GP21860@bombadil.infradead.org> <20190206202021.GQ21860@bombadil.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 06-02-19 15:54:01, Doug Ledford wrote: > On Wed, 2019-02-06 at 12:20 -0800, Matthew Wilcox wrote: > > On Wed, Feb 06, 2019 at 03:16:02PM -0500, Doug Ledford wrote: > > > On Wed, 2019-02-06 at 11:40 -0800, Matthew Wilcox wrote: > > > > On Wed, Feb 06, 2019 at 07:16:21PM +0000, Christopher Lameter wrote: > > > > > though? If we only allow this use case then we may not have to worry about > > > > > long term GUP because DAX mapped files will stay in the physical location > > > > > regardless. > > > > > > > > ... except for truncate. And now that I think about it, there was a > > > > desire to support hot-unplug which also needed revoke. > > > > > > We already support hot unplug of RDMA devices. But it is extreme. How > > > does hot unplug deal with a program running from the device (something > > > that would have returned ETXTBSY)? > > > > Not hot-unplugging the RDMA device but hot-unplugging an NV-DIMM. > > Is an NV-DIMM the only thing we use DAX on? Currently yes. However KVM people are soon going to use it for their purposes as well (essentially directly sharing host page cache between guests). Honza -- Jan Kara SUSE Labs, CR