diff options
author | Josef Bacik <josef@redhat.com> | 2010-03-19 14:07:23 -0400 |
---|---|---|
committer | Chris Mason <chris.mason@oracle.com> | 2010-03-30 21:19:09 -0400 |
commit | 287a0ab91d25ca982f895a76402e5893b47ed7a6 (patch) | |
tree | fcbe35daef2b4cbdc2bfc0c6026e7c45faef0245 /fs/lockd | |
parent | 1b1d1f6625e517a08640ddb4b8f8a0e025243fe3 (diff) |
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>
Diffstat (limited to 'fs/lockd')
0 files changed, 0 insertions, 0 deletions