Gitiles
Code Review Sign In
gerrit-public.fairphone.software / kernel / msm-4.9 / c9e27d94f5fc726f88897914025619fbfc18b23c / . / block / Kconfig
blob: 0cbb3b88b59afe7c89d2c71c042b18dda818759e [file] [log] [blame]
Jens Axboe3a65dfe2005-11-04 08:43:35 +0100[diff] [blame]1#
2# Block layer core configuration
3#
Jan Engelhardt16ed0022007-07-10 12:24:11 +0200[diff] [blame]4menuconfig BLOCK
Jens Axboe51d75132006-09-30 21:14:05 +0200[diff] [blame]5 bool "Enable the block layer" if EMBEDDED
David Howells93614012006-09-30 20:45:40 +0200[diff] [blame]6 default y
7 help
Nick Andrewee864182008-04-21 09:51:04 +0200[diff] [blame]8 Provide block layer support for the kernel.
David Howells93614012006-09-30 20:45:40 +0200[diff] [blame]9
Nick Andrewee864182008-04-21 09:51:04 +0200[diff] [blame]10 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 +0200[diff] [blame]20
21 Say Y here unless you know you really don't want to mount disks and
22 suchlike.
23
24if BLOCK
25
Jens Axboe3a65dfe2005-11-04 08:43:35 +0100[diff] [blame]26config LBD
Jens Axboeb3a6ffe2008-12-12 09:51:16 +0100[diff] [blame]27 bool "Support for large block devices and files"
Matthew Wilcoxe6243862006-12-04 03:38:31 -0700[diff] [blame]28 depends on !64BIT
Jens Axboe3a65dfe2005-11-04 08:43:35 +0100[diff] [blame]29 help
Jens Axboeb3a6ffe2008-12-12 09:51:16 +0100[diff] [blame]30 Enable block devices or files of size 2TB and larger.
Nick Andrewee864182008-04-21 09:51:04 +0200[diff] [blame]31
32 This option is required to support the full capacity of large
33 (2TB+) block devices, including RAID, disk, Network Block Device,
34 Logical Volume Manager (LVM) and loopback.
Jens Axboeb3a6ffe2008-12-12 09:51:16 +0100[diff] [blame]35
36 This option also enables support for single files larger than
37 2TB.
Nick Andrewee864182008-04-21 09:51:04 +0200[diff] [blame]38
Theodore Ts'o4d783b02009-01-06 15:16:33 -0500[diff] [blame]39 The ext4 filesystem requires that this feature be enabled in
40 order to support filesystems that have the huge_file feature
41 enabled. Otherwise, it will refuse to mount any filesystems
42 that use the huge_file feature, which is enabled by default
43 by mke2fs.ext4. The GFS2 filesystem also requires this feature.
44
Nick Andrewee864182008-04-21 09:51:04 +0200[diff] [blame]45 If unsure, say N.
Jens Axboe3a65dfe2005-11-04 08:43:35 +0100[diff] [blame]46
Jens Axboe2056a782006-03-23 20:00:26 +0100[diff] [blame]47config BLK_DEV_IO_TRACE
48 bool "Support for tracing block io actions"
Jens Axboe09540e62006-03-26 14:32:09 +0200[diff] [blame]49 depends on SYSFS
Jens Axboe2056a782006-03-23 20:00:26 +0100[diff] [blame]50 select RELAY
51 select DEBUG_FS
Arnaldo Carvalho de Melo5f3ea372008-10-30 08:34:33 +0100[diff] [blame]52 select TRACEPOINTS
Jens Axboe2056a782006-03-23 20:00:26 +0100[diff] [blame]53 help
Nick Andrewee864182008-04-21 09:51:04 +0200[diff] [blame]54 Say Y here if you want to be able to trace the block layer actions
Jens Axboe2056a782006-03-23 20:00:26 +0100[diff] [blame]55 on a given queue. Tracing allows you to see any traffic happening
Nick Andrewee864182008-04-21 09:51:04 +0200[diff] [blame]56 on a block device queue. For more information (and the userspace
57 support tools needed), fetch the blktrace tools from:
Jens Axboe2056a782006-03-23 20:00:26 +0100[diff] [blame]58
Jens Axboe75ce6fa2008-04-15 10:23:35 +0200[diff] [blame]59 git://git.kernel.dk/blktrace.git
Jens Axboe2056a782006-03-23 20:00:26 +0100[diff] [blame]60
Nick Andrewee864182008-04-21 09:51:04 +0200[diff] [blame]61 If unsure, say N.
62
Jens Axboe3d6392c2007-07-09 12:38:05 +0200[diff] [blame]63config BLK_DEV_BSG
FUJITA Tomonori319a7b72007-07-17 12:22:09 +0200[diff] [blame]64 bool "Block layer SG support v4 (EXPERIMENTAL)"
James Bottomley80ed71c2007-07-19 10:15:10 -0500[diff] [blame]65 depends on EXPERIMENTAL
Jens Axboe3d6392c2007-07-09 12:38:05 +0200[diff] [blame]66 ---help---
Nick Andrewee864182008-04-21 09:51:04 +0200[diff] [blame]67 Saying Y here will enable generic SG (SCSI generic) v4 support
68 for any block device.
FUJITA Tomonori319a7b72007-07-17 12:22:09 +0200[diff] [blame]69
Nick Andrewee864182008-04-21 09:51:04 +0200[diff] [blame]70 Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
71 can handle complicated SCSI commands: tagged variable length cdbs
72 with bidirectional data transfers and generic request/response
73 protocols (e.g. Task Management Functions and SMP in Serial
74 Attached SCSI).
75
76 If unsure, say N.
Jens Axboe3d6392c2007-07-09 12:38:05 +0200[diff] [blame]77
Martin K. Petersen7ba1ba12008-06-30 20:04:41 +0200[diff] [blame]78config BLK_DEV_INTEGRITY
79 bool "Block layer data integrity support"
80 ---help---
81 Some storage devices allow extra information to be
82 stored/retrieved to help protect the data. The block layer
83 data integrity option provides hooks which can be used by
84 filesystems to ensure better data integrity.
85
86 Say yes here if you have a storage device that provides the
87 T10/SCSI Data Integrity Field or the T13/ATA External Path
88 Protection. If in doubt, say N.
89
Linus Torvalds2b9e0aa2007-10-12 17:58:36 -0700[diff] [blame]90endif # BLOCK
91
Jens Axboe99874d52007-10-12 12:50:41 +0200[diff] [blame]92config BLOCK_COMPAT
93 bool
Linus Torvalds2b9e0aa2007-10-12 17:58:36 -0700[diff] [blame]94 depends on BLOCK && COMPAT
Jens Axboe99874d52007-10-12 12:50:41 +0200[diff] [blame]95 default y
96
Jens Axboe3a65dfe2005-11-04 08:43:35 +0100[diff] [blame]97source block/Kconfig.iosched