linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] Btrfs: save free space cache to the disk
Date: Mon, 20 Sep 2010 13:24:46 +0200	[thread overview]
Message-ID: <20100920112446.GA10866@attic.humilis.net> (raw)
In-Reply-To: <1284577734-3161-1-git-send-email-josef@redhat.com>

Josef Bacik wrote (ao):
> This patch series introduces the ability for btrfs to store the free space cache
> ondisk to make the caching of a block group much quicker.  Previously we had to
> search the entire extent-tree to look for gaps everytime we wanted to allocate
> in a block group.  This approach instead dumps all of the free space cache to
> disk for every dirtied block group each time we commit the transaction.  This is
> a disk format change, but in order to use the feature you will have to mount
> with -o space_cache, and then from then on you won't be able to use old kernels
> with your filesystem.

Will this go into a future version of btrfs?

If so, would it make sense to include other changes that would require a
format change?

	Sander

-- 
Humilis IT Services and Solutions
http://www.humilis.net

      parent reply	other threads:[~2010-09-20 11:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 19:08 [PATCH 0/3] Btrfs: save free space cache to the disk Josef Bacik
2010-09-15 19:08 ` [PATCH 1/3] Btrfs: create special free space cache inode FORMAT CHANGE Josef Bacik
2010-09-15 19:08 ` [PATCH 2/3] Btrfs: write out free space cache Josef Bacik
2010-09-15 19:08 ` [PATCH 3/3] Btrfs: load free space cache if it exists Josef Bacik
2010-09-20 11:24 ` Sander [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=20100920112446.GA10866@attic.humilis.net \
    --to=sander@humilis.net \
    --cc=josef@redhat.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).