2005-11-04 15:43:35 +08:00
|
|
|
#
|
|
|
|
|
# Block layer core configuration
|
|
|
|
|
#
|
|
|
|
|
#XXX - it makes sense to enable this only for 32-bit subarch's, not for x86_64
|
|
|
|
|
#for instance.
|
|
|
|
|
config LBD
|
|
|
|
|
bool "Support for Large Block Devices"
|
2006-01-06 16:19:28 +08:00
|
|
|
depends on X86 || (MIPS && 32BIT) || PPC32 || (S390 && !64BIT) || SUPERH || UML
|
2005-11-04 15:43:35 +08:00
|
|
|
help
|
|
|
|
|
Say Y here if you want to attach large (bigger than 2TB) discs to
|
|
|
|
|
your machine, or if you want to have a raid or loopback device
|
|
|
|
|
bigger than 2TB. Otherwise say N.
|
|
|
|
|
|
2006-03-24 03:00:26 +08:00
|
|
|
config BLK_DEV_IO_TRACE
|
|
|
|
|
bool "Support for tracing block io actions"
|
|
|
|
|
select RELAY
|
|
|
|
|
select DEBUG_FS
|
|
|
|
|
help
|
|
|
|
|
Say Y here, if you want to be able to trace the block layer actions
|
|
|
|
|
on a given queue. Tracing allows you to see any traffic happening
|
|
|
|
|
on a block device queue. For more information (and the user space
|
|
|
|
|
support tools needed), fetch the blktrace app from:
|
|
|
|
|
|
|
|
|
|
git://brick.kernel.dk/data/git/blktrace.git
|
|
|
|
|
|
2005-11-04 15:43:35 +08:00
|
|
|
source block/Kconfig.iosched
|
