From: Matthew Wilcox <willy@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
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: Re: [Lsf-pc] [LFS/MM TOPIC] fs reflink issues, fs online scrub/check, etc
Date: Tue, 21 Jan 2020 14:01:12 -0800 [thread overview]
Message-ID: <20200121220112.GB14467@bombadil.infradead.org> (raw)
In-Reply-To: <20200121161840.GA8236@magnolia>
On Tue, Jan 21, 2020 at 08:18:40AM -0800, Darrick J. Wong wrote:
> 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.
I still have Strong Opinions on how pagecache page sharing should be done
... and half a dozen more important projects ahead of it in my queue.
So I have no update on this.
next prev parent reply other threads:[~2020-01-21 22:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160210191715.GB6339@birch.djwong.org>
2016-02-10 19:18 ` [LFS/MM TOPIC] fs reflink issues, fs online scrub/check, etc Darrick J. Wong
2020-01-21 0:58 ` Steve French
2020-01-21 1:18 ` Qu Wenruo
2020-01-21 7:35 ` [Lsf-pc] " Amir Goldstein
2020-01-21 16:18 ` Darrick J. Wong
2020-01-21 22:01 ` Matthew Wilcox [this message]
2020-01-22 0:47 ` Dan Williams
2020-01-22 8: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=20200121220112.GB14467@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=amir73il@gmail.com \
--cc=darrick.wong@oracle.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).