linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>
Subject: Re: [GIT PULL] overlayfs update for 4.14
Date: Mon, 18 Sep 2017 07:27:05 +1000	[thread overview]
Message-ID: <20170917212705.GB17782@dastard> (raw)
In-Reply-To: <CAJfpeguB=H=FNyMDyyO4417o1DSiw-5RS0S3nzENHiCRiqmYRQ@mail.gmail.com>

On Fri, Sep 15, 2017 at 10:06:24AM +0200, Miklos Szeredi wrote:
> or some way to have a shared page
> cache that's breakable on copy up, which does not look trivial at all.

If we get that, it will come through overlay using reflink for
copyup and filesystems doing the page cache sharing of multiply
referenced data blocks. I don't see overlay being involved in this
functionality at all....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2017-09-17 21:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 14:05 [GIT PULL] overlayfs update for 4.14 Miklos Szeredi
2017-09-13 16:25 ` Linus Torvalds
2017-09-14  6:46   ` Miklos Szeredi
2017-09-14 20:00     ` Linus Torvalds
2017-09-14 20:12       ` Miklos Szeredi
2017-09-14 20:24         ` Linus Torvalds
2017-09-15  7:32           ` Miklos Szeredi
2017-09-15  8:06             ` Miklos Szeredi
2017-09-17 21:27               ` Dave Chinner [this message]
2017-09-15 18:35             ` Linus Torvalds
2017-09-17 14:38       ` J. R. Okajima

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=20170917212705.GB17782@dastard \
    --to=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).