diff options
| author | Chris Mason <chris.mason@oracle.com> | 2011-04-15 16:05:44 -0400 |
|---|---|---|
| committer | Chris Mason <chris.mason@oracle.com> | 2011-04-15 16:05:44 -0400 |
| commit | 0e4f8f888845f9dca540ad175884244e5db5eea2 (patch) | |
| tree | cc43a4a6ff229a84f26376f27d9d938ac4dc1b26 /fs/btrfs/extent_io.c | |
| parent | 329c5056be8774255db04b01242a9ff4f02eb8ea (diff) | |
| download | kernel_samsung_smdk4412-0e4f8f888845f9dca540ad175884244e5db5eea2.zip kernel_samsung_smdk4412-0e4f8f888845f9dca540ad175884244e5db5eea2.tar.gz kernel_samsung_smdk4412-0e4f8f888845f9dca540ad175884244e5db5eea2.tar.bz2 | |
Btrfs: don't force chunk allocation in find_free_extent
find_free_extent likes to allocate in contiguous clusters,
which makes writeback faster, especially on SSD storage. As
the FS fragments, these clusters become harder to find and we have
to decide between allocating a new chunk to make more clusters
or giving up on the cluster to allocate from the free space
we have.
Right now it creates too many chunks, and you can end up with
a whole FS that is mostly empty metadata chunks. This commit
changes the allocation code to be more strict and only
allocate new chunks when we've made good use of the chunks we
already have.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/btrfs/extent_io.c')
0 files changed, 0 insertions, 0 deletions