From: Darrick J. Wong <darrick.wong@oracle.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Steve French <smfrench@gmail.com>,
lsf-pc@lists.linux-foundation.org,
xfs <xfs@e29208.dscx.akamaiedge.net>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [Lsf-pc] [LFS/MM TOPIC] fs reflink issues, fs online scrub/check, etc
Date: Tue, 21 Jan 2020 08:18:40 -0800 [thread overview]
Message-ID: <20200121161840.GA8236@magnolia> (raw)
In-Reply-To: <CAOQ4uxjd-YWe5uHqfSW9iSdw-hQyFCwo84cK8ebJVJSY_vda3Q@mail.gmail.com>
On Tue, Jan 21, 2020 at 09:35:22AM +0200, Amir Goldstein wrote:
> On Tue, Jan 21, 2020 at 3:19 AM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
> >
> > Didn't see the original mail, so reply here.
>
> Heh! Original email was from 2016, but most of Darrick's wish list is
> still relevant in 2020 :)
Grumble grumble stable behavior of clonerange/deduperange ioctls across
filesystems grumble grumble.
> I for one would be very interested in getting an update on the
> progress of pagecache
> page sharing if there is anyone working on it.
Me too. I guess it's the 21st, I should really send in a proposal for
*this year's* LSFMMBPFLOLBBQ.
--D
> Thanks,
> Amir.
next prev parent reply other threads:[~2020-01-21 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160210191715.GB6339@birch.djwong.org>
2016-02-10 19:18 ` [Ocfs2-devel] [LFS/MM TOPIC] fs reflink issues, fs online scrub/check, etc Darrick J. Wong
2020-01-21 0:58 ` Steve French
[not found] ` <0089aff3-c4d3-214e-30d7-012abf70623a@gmx.com>
[not found] ` <CAOQ4uxjd-YWe5uHqfSW9iSdw-hQyFCwo84cK8ebJVJSY_vda3Q@mail.gmail.com>
2020-01-21 16:18 ` Darrick J. Wong [this message]
[not found] ` <20200121220112.GB14467@bombadil.infradead.org>
[not found] ` <CAPcyv4iPX4fDZGFwCkJxMDc-+1DjOMVZYVqnE=XTZpis6ZLFww@mail.gmail.com>
2020-01-22 8:21 ` [Ocfs2-devel] [Lsf-pc] " 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=20200121161840.GA8236@magnolia \
--to=darrick.wong@oracle.com \
--cc=amir73il@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=quwenruo.btrfs@gmx.com \
--cc=smfrench@gmail.com \
--cc=xfs@e29208.dscx.akamaiedge.net \
/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).