Btrfs: kill max_extent mount option
authorJosef Bacik <josef@redhat.com>
Fri, 19 Mar 2010 18:07:23 +0000 (18:07 +0000)
committerChris Mason <chris.mason@oracle.com>
Wed, 31 Mar 2010 01:19:09 +0000 (21:19 -0400)
commit287a0ab91d25ca982f895a76402e5893b47ed7a6
treefcbe35daef2b4cbdc2bfc0c6026e7c45faef0245
parent1b1d1f6625e517a08640ddb4b8f8a0e025243fe3
Btrfs: kill max_extent mount option

As Yan pointed out, theres not much reason for all this complicated math to
account for file extents being split up into max_extent chunks, since they are
likely to all end up in the same leaf anyway.  Since there isn't much reason to
use max_extent, just remove the option altogether so we have one less thing we
need to test.

Signed-off-by: Josef Bacik <josef@redhat.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
fs/btrfs/ctree.h
fs/btrfs/disk-io.c
fs/btrfs/extent-tree.c
fs/btrfs/inode.c
fs/btrfs/ordered-data.c
fs/btrfs/super.c