summaryrefslogtreecommitdiff
path: root/block/Kconfig
blob: 9af6c614dfde8cc8118d1b8c21f2f24f53e8ef8a (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
#
# Block layer core configuration
#
config BLOCK
       bool "Enable the block layer"
       default y
       help
	 This permits the block layer to be removed from the kernel if it's not
	 needed (on some embedded devices for example).  If this option is
	 disabled, then blockdev files will become unusable and some
	 filesystems (such as ext3) will become unavailable.

	 This option will also disable SCSI character devices and USB storage
	 since they make use of various block layer definitions and
	 facilities.

	 Say Y here unless you know you really don't want to mount disks and
	 suchlike.

if BLOCK

#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"
	depends on X86 || (MIPS && 32BIT) || PPC32 || (S390 && !64BIT) || SUPERH || UML
	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.

config BLK_DEV_IO_TRACE
	bool "Support for tracing block io actions"
	depends on SYSFS
	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

config LSF
	bool "Support for Large Single Files"
	depends on X86 || (MIPS && 32BIT) || PPC32 || ARCH_S390_31 || SUPERH || UML
	help
	  Say Y here if you want to be able to handle very large files (bigger
	  than 2TB), otherwise say N.

	  If unsure, say Y.

endif

source block/Kconfig.iosched