From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id CAB8020886F38 for ; Thu, 14 Feb 2019 12:34:15 -0800 (PST) Date: Thu, 14 Feb 2019 15:34:12 -0500 From: Jerome Glisse Subject: Re: [Lsf-pc] [LSF/MM TOPIC] The end of the DAX experiment Message-ID: <20190214203411.GC3420@redhat.com> References: <20190214134622.GG4525@dhcp22.suse.cz> <20190214191013.GA3420@redhat.com> <20190214200840.GB12668@bombadil.infradead.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Dan Williams Cc: lsf-pc@lists.linux-foundation.org, linux-nvdimm , Linux Kernel Mailing List , Matthew Wilcox , Michal Hocko , linux-xfs , linux-fsdevel , linux-ext4 List-ID: On Thu, Feb 14, 2019 at 12:20:11PM -0800, Dan Williams wrote: > On Thu, Feb 14, 2019 at 12:09 PM Matthew Wilcox wro= te: > > > > On Thu, Feb 14, 2019 at 11:31:24AM -0800, Dan Williams wrote: > > > On Thu, Feb 14, 2019 at 11:10 AM Jerome Glisse w= rote: > > > > I am just again working on my struct page mapping patchset as well = as > > > > the generic page write protection that sits on top. I hope to be ab= le > > > > to post the v2 in couple weeks. You can always look at my posting l= ast > > > > year to see more details. > > > > > > Yes, I have that in mind as one of the contenders. However, it's not > > > clear to me that its a suitable fit for filesystem-reflink. Others > > > have floated the 'page proxy' idea, so it would be good to discuss the > > > merits of the general approaches. > > > > ... and my preferred option of putting pfn entries in the page cache. > = > Another option to include the discussion. > = > > Or is that what you meant by "page proxy"? > = > Page proxy would be an object that a filesystem could allocate to > point back to a single physical 'struct page *'. The proxy would > contain an override for page->index. Note that generic page write protection has such object, kind of like stable_node in KSM. You overwritte page->mapping to point to this generic struct which has a pointer to set of callback so that whatever is protecting the page can offer API to break protection (break sharing here). So instead of having struct proxy_page -> struct page you would have the reverse: struct page -> struct proxy and so you do not have to change much in all the file system beside removing the reliance on page->mapping which is what most of my patches are about. Cheers, J=E9r=F4me _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm