From: Andreas Dilger <adilger@dilger.ca>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-btrfs@vger.kernel.org, lsf-pc@lists.linux-foundation.org
Subject: Re: [LSF/MM TOPIC] sharing pages between mappings
Date: Wed, 11 Jan 2017 13:35:02 -0700 [thread overview]
Message-ID: <F2092AFE-A2C8-438E-A8AA-4D74509344F5@dilger.ca> (raw)
In-Reply-To: <CAJfpegv9EhT4Y3QjTZBHoMKSiVGtfmTGPhJp_rh3a7=rFCHu5A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
On Jan 11, 2017, at 3:29 AM, Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> I know there's work on this for xfs, but could this be done in generic mm code?
>
> What are the obstacles? page->mapping and page->index are the obvious ones.
>
> If that's too difficult is it maybe enough to share mappings between
> files while they are completely identical and clone the mapping when
> necessary?
>
> All COW filesystems would benefit, as well as layered ones: lots of
> fuse fs, and in some cases overlayfs too.
For layered filesystems it would also be useful to have an API to move
pages between mappings easily.
> Related: what can DAX do in the presence of cloned block?
>
> Thanks,
> Miklos
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-01-11 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 10:29 Miklos Szeredi
2017-01-11 11:51 ` [Lsf-pc] " Jan Kara
2017-01-11 14:13 ` Miklos Szeredi
2017-01-17 15:46 ` Jan Kara
2017-01-11 18:05 ` Darrick J. Wong
2017-01-11 20:35 ` Andreas Dilger [this message]
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=F2092AFE-A2C8-438E-A8AA-4D74509344F5@dilger.ca \
--to=adilger@dilger.ca \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=miklos@szeredi.hu \
/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