linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Bartell <wingedtachikoma@gmail.com>
To: "Yan, Zheng " <yanzheng@21cn.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/4] btrfs-convert: make more use of cache_free_extents
Date: Tue, 18 May 2010 12:18:19 -0400	[thread overview]
Message-ID: <20100518161819.GB4380@flcl.lan> (raw)
In-Reply-To: <AANLkTikJiGhwyOV3UTiS9vdjVX4w3yuVT2urOdXSZ8sD@mail.gmail.com>

On Tue, May 18, 2010 at 09:40:28PM +0800, Yan, Zheng  wrote:
> On Sat, Mar 20, 2010 at 12:24 PM, Sean Bartell
> <wingedtachikoma@gmail.com> wrote:
> > An extent_io_tree is used for all free space information. This allo=
ws
> > removal of ext2_alloc_block and ext2_free_block, and makes
> > create_ext2_image less ext2-specific.

> > + =A0 =A0 =A0 ret =3D ext2_cache_free_extents(ext2_fs, &orig_free_t=
ree);
> > + =A0 =A0 =A0 if (ret) {
> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 fprintf(stderr, "error during cache_f=
ree_extents %d\n", ret);
> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 goto fail;
> > + =A0 =A0 =A0 }
> > + =A0 =A0 =A0 /* preserve first 64KiB, just in case */
> > + =A0 =A0 =A0 clear_extent_dirty(&orig_free_tree, 0, BTRFS_SUPER_IN=
=46O_OFFSET - 1, 0);
> > +
> > + =A0 =A0 =A0 ret =3D copy_dirtiness(&free_tree, &orig_free_tree);
> > + =A0 =A0 =A0 if (ret) {
> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 fprintf(stderr, "error during copy_di=
rtiness %d\n", ret);
> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 goto fail;
> > + =A0 =A0 =A0 }

> extent_io_tree is not very space efficient. caching free space in
> several places is not good. I prefer adding a function that checks
> if a given block is used to the 'convert_fs' structure.

Good point. I'll change cache_free_extents to something like
  int (*iterate_used_extents)(struct convert_fs *fs, u64 start, u64 end=
,
                              void *priv, int (*cb)(u64 start, u64 end)=
)
create_image_file_range and do_convert should work well with a callback=
=2E

This also opens up the possibility of finding free extents
incrementally: call iterate_used_extents on the first GB, then
custom_alloc_extent will call it on the next GB once free space runs
out.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-05-18 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20  4:24 [PATCH 1/4] btrfs-convert: make more use of cache_free_extents Sean Bartell
2010-05-18 13:40 ` Yan, Zheng 
2010-05-18 16:18   ` Sean Bartell [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=20100518161819.GB4380@flcl.lan \
    --to=wingedtachikoma@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=yanzheng@21cn.com \
    /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).