From: Chris Mason <clm@fb.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Chandan Rajendra <chandan@linux.vnet.ibm.com>,
<lsf-pc@lists.linux-foundation.org>,
<linux-fsdevel@vger.kernel.org>, <linux-btrfs@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC]: Btrfs: Decoupling block-size and page-size in BTRFS.
Date: Mon, 1 Dec 2014 09:06:53 -0500 [thread overview]
Message-ID: <1417442813.14154.0@mail.thefacebook.com> (raw)
In-Reply-To: <20141201101353.GA763@infradead.org>
On Mon, Dec 1, 2014 at 5:13 AM, Christoph Hellwig <hch@infradead.org>
wrote:
> Is this topic relevant for the broarder FS community? Maybe the btrfs
> community should look into organizing a meeting co-hosted with Vault
> similar to what we did for ext4 and XFS in the past?
Yeah, this is a very btrfs specific topic. I'm happy to organize an
official Btrfs sub-topic as part of vault or LSF.
-chris
prev parent reply other threads:[~2014-12-01 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 7:13 [LSF/MM TOPIC]: Btrfs: Decoupling block-size and page-size in BTRFS Chandan Rajendra
2014-12-01 10:13 ` [Lsf-pc] " Christoph Hellwig
2014-12-01 14:06 ` Chris Mason [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=1417442813.14154.0@mail.thefacebook.com \
--to=clm@fb.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@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).