From: bfields@fieldses.org (J. Bruce Fields)
To: Dave Chinner <david@fromorbit.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] Virtual block address space mapping
Date: Wed, 31 Jan 2018 21:23:32 -0500 [thread overview]
Message-ID: <20180201022332.GD3814@fieldses.org> (raw)
In-Reply-To: <20180129100834.rhpgnz5572zxmqep@destitution>
On Mon, Jan 29, 2018 at 09:08:34PM +1100, Dave Chinner wrote:
> I've implemented both sides on XFS to provide the capability for an
> XFS filesystem to host XFS subvolumes. however, this is an abstract
> interface and so if someone modifies ext4 to use a virtual block
> address space, then XFS will be able to host cloneable ext4
> subvolumes, too. :P
This sounds really interesting.
Would it be possible to write up a brief summary of your current
interface? Even if it's not completely correct it might be a useful
starting point.
--b.
next prev parent reply other threads:[~2018-02-01 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 10:08 [LSF/MM TOPIC] Virtual block address space mapping Dave Chinner
2018-01-31 21:25 ` Darrick J. Wong
2018-02-01 2:01 ` Dave Chinner
2018-02-01 2:23 ` J. Bruce Fields [this message]
2018-02-01 5:21 ` Dave Chinner
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=20180201022332.GD3814@fieldses.org \
--to=bfields@fieldses.org \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).