From: Josef Bacik <josef@redhat.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] Btrfs: save free space cache to the disk V2
Date: Wed, 22 Sep 2010 14:39:39 -0400 [thread overview]
Message-ID: <1285180782-29364-1-git-send-email-josef@redhat.com> (raw)
V1->V2
- This includes my previous fix for the Incompat flags that I posted earlier
- Fix kunmap() to use the page and not the vaddr, I messed this up when going
from kmap_atomic to kmap
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. You can pull these patches from my git tree
git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-work.git
and they should pull right onto Chris's btrfs-unstable tree. Please test this
as it's a big change and I can only test so much. That being said this has been
run through xfstests thoroughly and I've been running it on a VM with btrfs as
root. Thanks,
Josef
next reply other threads:[~2010-09-22 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 18:39 Josef Bacik [this message]
2010-09-22 18:39 ` [PATCH 1/3] Btrfs: create special free space cache inode FORMAT CHANGE Josef Bacik
2010-09-22 18:39 ` [PATCH 2/3] Btrfs: write out free space cache Josef Bacik
2010-09-22 18:39 ` [PATCH 3/3] Btrfs: load free space cache if it exists Josef Bacik
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=1285180782-29364-1-git-send-email-josef@redhat.com \
--to=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).