| commit | 0b4a9d248f88e6773312f262e8185f23863d984a | |
| author | Josef Bacik <josef@redhat.com> | |
| Thu, 26 Jan 2012 20:01:11 +0000 (26 15:01 -0500) | ||
| committer | Chris Mason <chris.mason@oracle.com> | |
| Thu, 26 Jan 2012 20:01:11 +0000 (26 15:01 -0500) | ||
| tree | bd822950b56730d6be409c98291c4f2ba19678dc | treesnapshot (tar.gz zip) |
| parent | 8bedd51b6121c4607784d75f852828d25d119c52 | commitdiff |
Btrfs: use cluster->window_start when allocating from a cluster bitmap
We specifically set window_start in the cluster struct to indicate where the
cluster starts in a bitmap, but we've been using min_start to indicate where
we're searching from. This is usually the start of the blockgroup, so
essentially means we're constantly searching from the start of any bitmap we
find, which completely negates all the trouble we go to in order to setup a
cluster. So start using window_start to make sure we actually use the area we
found. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
We specifically set window_start in the cluster struct to indicate where the
cluster starts in a bitmap, but we've been using min_start to indicate where
we're searching from. This is usually the start of the blockgroup, so
essentially means we're constantly searching from the start of any bitmap we
find, which completely negates all the trouble we go to in order to setup a
cluster. So start using window_start to make sure we actually use the area we
found. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
| fs/btrfs/free-space-cache.c | diffblobblamehistory |