|author||Jens Axboe <firstname.lastname@example.org>||2008-12-12 09:51:16 +0100|
|committer||Jens Axboe <email@example.com>||2008-12-29 08:29:51 +0100|
Get rid of CONFIG_LSF
We have two seperate config entries for large devices/files. One is CONFIG_LBD that guards just the devices, the other is CONFIG_LSF that handles large files. This doesn't make a lot of sense, you typically want both or none. So get rid of CONFIG_LSF and change CONFIG_LBD wording to indicate that it covers both. Acked-by: Jean Delvare <firstname.lastname@example.org> Signed-off-by: Jens Axboe <email@example.com>
Diffstat (limited to 'block/Kconfig')
1 files changed, 5 insertions, 18 deletions
diff --git a/block/Kconfig b/block/Kconfig
index 290b219..ac0956f 100644
@@ -24,21 +24,17 @@ menuconfig BLOCK
- bool "Support for Large Block Devices"
+ bool "Support for large block devices and files"
depends on !64BIT
- Enable block devices of size 2TB and larger.
+ Enable block devices or files of size 2TB and larger.
This option is required to support the full capacity of large
(2TB+) block devices, including RAID, disk, Network Block Device,
Logical Volume Manager (LVM) and loopback.
- For example, RAID devices are frequently bigger than the capacity
- of the largest individual hard drive.
- This option is not required if you have individual disk drives
- which total 2TB+ and you are not aggregating the capacity into
- a large block device (e.g. using RAID or LVM).
+ This option also enables support for single files larger than
If unsure, say N.
@@ -58,15 +54,6 @@ config BLK_DEV_IO_TRACE
If unsure, say N.
- bool "Support for Large Single Files"
- depends on !64BIT
- Say Y here if you want to be able to handle very large files (2TB
- and larger), otherwise say N.
- If unsure, say Y.
bool "Block layer SG support v4 (EXPERIMENTAL)"
depends on EXPERIMENTAL