From: Liu Bo <bo.li.liu@oracle.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"dave@jikos.cz" <dave@jikos.cz>
Subject: Re: [PATCH v2 2/2] Btrfs: snapshot-aware defrag
Date: Thu, 6 Sep 2012 22:13:27 +0800 [thread overview]
Message-ID: <20120906141327.GA18524@liubo> (raw)
In-Reply-To: <20120906131153.GB18438@localhost.localdomain>
On Thu, Sep 06, 2012 at 09:11:53AM -0400, Josef Bacik wrote:
> On Wed, Sep 05, 2012 at 07:10:52PM -0600, Liu Bo wrote:
> > This comes from one of btrfs's project ideas,
> > As we defragment files, we break any sharing from other snapshots.
> > The balancing code will preserve the sharing, and defrag needs to grow this
> > as well.
> >
> > Now we're able to fill the blank with this patch, in which we make full use of
> > backref walking stuff.
> >
> > Here is the basic idea,
> > o set the writeback ranges started by defragment with flag EXTENT_DEFRAG
> > o at endio, after we finish updating fs tree, we use backref walking to find
> > all parents of the ranges and re-link them with the new COWed file layout by
> > adding corresponding backrefs.
> >
> > Original-Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> > ---
> > v2: rebase against the latest btrfs-repo
> >
>
> Heh well it doesn't apply onto btrfs-next, try again please :). Thanks,
>
> Josef
oh, sorry for the trouble, I'll redo a btrfs-next version :)
thanks,
liubo
next prev parent reply other threads:[~2012-09-06 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 1:10 [PATCH v2 1/2] Btrfs: use flag EXTENT_DEFRAG for snapshot-aware defrag Liu Bo
2012-09-06 1:10 ` [PATCH v2 2/2] Btrfs: " Liu Bo
2012-09-06 13:11 ` Josef Bacik
2012-09-06 14:13 ` Liu Bo [this message]
2012-09-06 14:26 ` Liu Bo
2012-09-10 23:49 ` David Sterba
2012-09-11 15:00 ` Liu Bo
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=20120906141327.GA18524@liubo \
--to=bo.li.liu@oracle.com \
--cc=dave@jikos.cz \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.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).