From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org,
Al Viro <viro@zeniv.linux.org.uk>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
Matthew Wilcox <willy@infradead.org>, Chris Mason <clm@fb.com>,
Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>, Jerome Glisse <jglisse@redhat.com>
Subject: Re: [LSF/MM TOPIC] Sharing file backed pages
Date: Wed, 23 Jan 2019 15:54:34 +0100 [thread overview]
Message-ID: <20190123145434.GK13149@quack2.suse.cz> (raw)
In-Reply-To: <CAOQ4uxj4DiU=vFqHCuaHQ=4XVkTeJrXci0Y6YUX=22dE+iygqA@mail.gmail.com>
On Wed 23-01-19 10:48:58, Amir Goldstein wrote:
> In his session about "reflink" in LSF/MM 2016 [1], Darrick Wong brought
> up the subject of sharing pages between cloned files and the general vibe
> in room was that it could be done.
>
> In his talk about XFS subvolumes and snapshots [2], Dave Chinner said
> that Matthew Willcox was "working on that problem".
>
> I have started working on a new overlayfs address space implementation
> that could also benefit from being able to share pages even for filesystems
> that do not support clones (for copy up anticipation state).
>
> To simplify the problem, we can start with sharing only uptodate clean
> pages that map the same offset in respected files. While the same offset
> requirement somewhat limits the use cases that benefit from shared file
> pages, there is still a vast majority of use cases (i.e. clone full
> image), where sharing pages of similar offset will bring a lot of
> benefit.
>
> At first glance, this requires dropping the assumption that a for an
> uptodate clean page, vmf->vma->vm_file->f_inode == page->mapping->host.
> Is there really such an assumption in common vfs/mm code? and what will
> it take to drop it?
There definitely is such assumption. Take for example page reclaim as one
such place that will be non-trivial to deal with. You need to remove the
page from page cache of all inodes that contain it without having any file
context whatsoever. So you will need to create some way for this page->page
caches mapping to happen. Jerome in his talk at LSF/MM last year [1] actually
nicely summarized what it would take to get rid of page->mapping
dereferences. He even had some preliminary patches. To sum it up, it's a
lot of intrusive work but in principle it is possible.
[1] https://lwn.net/Articles/752564/
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2019-01-23 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 8:48 [LSF/MM TOPIC] Sharing file backed pages Amir Goldstein
2019-01-23 14:54 ` Jan Kara [this message]
2019-01-23 15:12 ` Jerome Glisse
2019-01-23 15:26 ` Jerome Glisse
2019-01-23 17:57 ` Amir Goldstein
2019-01-24 10:39 ` Kirill A. Shutemov
2019-01-25 8:39 ` Amir Goldstein
2019-01-23 17:06 ` James Bottomley
2019-01-23 19:10 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190123145434.GK13149@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=clm@fb.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=jglisse@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).