All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Shao Miller <shao.miller@treefrog.ca>
Cc: clm@fb.com, dm-devel@redhat.com
Subject: Re: Shared Memory Pages for Same Base Device
Date: Mon, 22 Sep 2014 10:26:27 -0400	[thread overview]
Message-ID: <20140922142626.GB5698@redhat.com> (raw)
In-Reply-To: <54202D4D.1030901@treefrog.ca>

On Mon, Sep 22 2014 at 10:08am -0400,
Shao Miller <shao.miller@treefrog.ca> wrote:

> On 9/22/2014 9:08 AM, Mike Snitzer wrote:
> >
> >Unfortunately device-mapper thin provisioning doesn't offer shared
> >pagecache pages across snapshot volumes.  This is a block layer
> >limitation (the block layer doesn't allow pages to be shared across
> >block devices, and dm-thinp snapshot volumes are each a block device).
> >Modifying the VM, block and DM subsystems to provide this capability is
> >not an easy task and as such is really not a near-term priority.
> 
> I sincerely appreciate your response, Mike.  I figured as much, but
> hopefully this thread will be useful to future searchers.
> 
> >Interestingly BTRFS does _not_ offer this page sharing either.  I'm told
> >that the only emerging solution for this is overlayfs.
> This is very surprising.  I've just done some testing and
> /proc/PID/maps for the same binary from two different snapshots
> deriving from the same base do show the same block-device major and
> minor, with the same offset.  Do you happen to have a reference for
> that detail about BTRFS, or perhaps an idea for the right venue to
> learn more about that?  Unfortunately, I guess it's off-topic for
> device-mapper.

I learned as much from Chris Mason (cc'd) in a FB thread I started on
this very topic.  Chris said:

"It would be awesome if we had a way to share page cache pages cow style
across filesystem snapshots. Every file ends up with its own address
space, so we really need to just share the pages. It's complex though"
 
> Also unfortunately, it seems that overlayfs isn't mainline Linux nor
> out-of-the-box for some distributions.  (Like CentOS 7.)
> 
> I enjoy device-mapper for CoW iSCSI and AoE.  Keep up the great work, folks!

Thanks

      reply	other threads:[~2014-09-22 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-20 15:50 Shared Memory Pages for Same Base Device Shao Miller
2014-09-22 13:08 ` Mike Snitzer
2014-09-22 14:08   ` Shao Miller
2014-09-22 14:26     ` Mike Snitzer [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=20140922142626.GB5698@redhat.com \
    --to=snitzer@redhat.com \
    --cc=clm@fb.com \
    --cc=dm-devel@redhat.com \
    --cc=shao.miller@treefrog.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.