blob: e20fbde0875c6154fc8deaa96df64844f67c4bfc [file] [log] [blame]
Jens Axboe3a65dfe2005-11-04 08:43:35 +01001#
2# Block layer core configuration
3#
Jan Engelhardt16ed0022007-07-10 12:24:11 +02004menuconfig BLOCK
Jens Axboe51d75132006-09-30 21:14:05 +02005 bool "Enable the block layer" if EMBEDDED
David Howells93614012006-09-30 20:45:40 +02006 default y
7 help
Nick Andrewee864182008-04-21 09:51:04 +02008 Provide block layer support for the kernel.
David Howells93614012006-09-30 20:45:40 +02009
Nick Andrewee864182008-04-21 09:51:04 +020010 Disable this option to remove the block layer support from the
11 kernel. This may be useful for embedded devices.
12
13 If this option is disabled:
14
15 - block device files will become unusable
16 - some filesystems (such as ext3) will become unavailable.
17
18 Also, SCSI character devices and USB storage will be disabled since
19 they make use of various block layer definitions and facilities.
David Howells93614012006-09-30 20:45:40 +020020
21 Say Y here unless you know you really don't want to mount disks and
22 suchlike.
23
24if BLOCK
25
Bartlomiej Zolnierkiewicz90c699a2009-06-19 08:08:50 +020026config LBDAF
27 bool "Support for large (2TB+) block devices and files"
Matthew Wilcoxe6243862006-12-04 03:38:31 -070028 depends on !64BIT
Bartlomiej Zolnierkiewiczdb29a6b2009-04-21 09:27:03 +020029 default y
Jens Axboe3a65dfe2005-11-04 08:43:35 +010030 help
Jens Axboeb3a6ffe2008-12-12 09:51:16 +010031 Enable block devices or files of size 2TB and larger.
Nick Andrewee864182008-04-21 09:51:04 +020032
33 This option is required to support the full capacity of large
34 (2TB+) block devices, including RAID, disk, Network Block Device,
35 Logical Volume Manager (LVM) and loopback.
Jens Axboeb3a6ffe2008-12-12 09:51:16 +010036
37 This option also enables support for single files larger than
38 2TB.
Nick Andrewee864182008-04-21 09:51:04 +020039
Theodore Ts'o4d783b02009-01-06 15:16:33 -050040 The ext4 filesystem requires that this feature be enabled in
41 order to support filesystems that have the huge_file feature
Bartlomiej Zolnierkiewiczdb29a6b2009-04-21 09:27:03 +020042 enabled. Otherwise, it will refuse to mount in the read-write
43 mode any filesystems that use the huge_file feature, which is
44 enabled by default by mke2fs.ext4.
Theodore Ts'o4d783b02009-01-06 15:16:33 -050045
Bartlomiej Zolnierkiewiczdb29a6b2009-04-21 09:27:03 +020046 The GFS2 filesystem also requires this feature.
47
48 If unsure, say Y.
Jens Axboe3a65dfe2005-11-04 08:43:35 +010049
Jens Axboe3d6392c2007-07-09 12:38:05 +020050config BLK_DEV_BSG
John Stoffel14d9fa32009-08-04 22:10:17 +020051 bool "Block layer SG support v4"
52 default y
53 help
Nick Andrewee864182008-04-21 09:51:04 +020054 Saying Y here will enable generic SG (SCSI generic) v4 support
55 for any block device.
FUJITA Tomonori319a7b72007-07-17 12:22:09 +020056
Nick Andrewee864182008-04-21 09:51:04 +020057 Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
58 can handle complicated SCSI commands: tagged variable length cdbs
59 with bidirectional data transfers and generic request/response
60 protocols (e.g. Task Management Functions and SMP in Serial
61 Attached SCSI).
62
John Stoffel14d9fa32009-08-04 22:10:17 +020063 This option is required by recent UDEV versions to properly
64 access device serial numbers, etc.
65
66 If unsure, say Y.
Jens Axboe3d6392c2007-07-09 12:38:05 +020067
Martin K. Petersen7ba1ba12008-06-30 20:04:41 +020068config BLK_DEV_INTEGRITY
69 bool "Block layer data integrity support"
70 ---help---
71 Some storage devices allow extra information to be
72 stored/retrieved to help protect the data. The block layer
73 data integrity option provides hooks which can be used by
74 filesystems to ensure better data integrity.
75
76 Say yes here if you have a storage device that provides the
77 T10/SCSI Data Integrity Field or the T13/ATA External Path
78 Protection. If in doubt, say N.
79
Vivek Goyal31e4c282009-12-03 12:59:42 -050080config BLK_CGROUP
81 bool
82 depends on CGROUPS
83 default n
84 ---help---
85 Generic block IO controller cgroup interface. This is the common
86 cgroup interface which should be used by various IO controlling
87 policies.
88
89 Currently, CFQ IO scheduler uses it to recognize task groups and
90 control disk bandwidth allocation (proportional time slice allocation)
91 to such task groups.
92
Vivek Goyal2868ef72009-12-03 12:59:48 -050093config DEBUG_BLK_CGROUP
94 bool
95 depends on BLK_CGROUP
96 default n
97 ---help---
98 Enable some debugging help. Currently it stores the cgroup path
99 in the blk group which can be used by cfq for tracing various
100 group related activity.
101
Linus Torvalds2b9e0aa2007-10-12 17:58:36 -0700102endif # BLOCK
103
Jens Axboe99874d52007-10-12 12:50:41 +0200104config BLOCK_COMPAT
105 bool
Linus Torvalds2b9e0aa2007-10-12 17:58:36 -0700106 depends on BLOCK && COMPAT
Jens Axboe99874d52007-10-12 12:50:41 +0200107 default y
108
Jens Axboe3a65dfe2005-11-04 08:43:35 +0100109source block/Kconfig.iosched