linux-toradex.git/block/Kconfig, branch v2.6.34

block: make CONFIG_BLK_CGROUP visible

2010-03-16T07:57:15+00:00

Make the config visible, so we can choose from CONFIG_BLK_CGROUP=y
and CONFIG_BLK_CGROUP=m when CONFIG_IOSCHED_CFQ=m.

Signed-off-by: Li Zefan 
Signed-off-by: Jens Axboe

blkio: Some debugging aids for CFQ

2009-12-03T18:28:52+00:00

o Some debugging aids for CFQ.

Signed-off-by: Vivek Goyal 
Signed-off-by: Jens Axboe

blkio: Introduce blkio controller cgroup interface

2009-12-03T18:28:51+00:00

o This is basic implementation of blkio controller cgroup interface. This is
  the common interface visible to user space and should be used by different
  IO control policies as we implement those.

Signed-off-by: Vivek Goyal 
Signed-off-by: Jens Axboe

Make SCSI SG v4 driver enabled by default and remove EXPERIMENTAL dependency, since udev depends on BSG

2009-08-04T20:10:17+00:00

Make Block Layer SG support v4 the default, since recent udev versions
depend on this to access serial numbers and other low level info properly.

This should be backported to older kernels as well, since most distros have
enabled this for a long time.

Signed-off-by: John Stoffel 
Cc: stable@kernel.org
Signed-off-by: Jens Axboe

block: rename CONFIG_LBD to CONFIG_LBDAF

2009-06-19T06:08:50+00:00

Follow-up to "block: enable by default support for large devices
and files on 32-bit archs".

Rename CONFIG_LBD to CONFIG_LBDAF to:
- allow update of existing [def]configs for "default y" change
- reflect that it is used also for large files support nowadays

Signed-off-by: Bartlomiej Zolnierkiewicz 
Signed-off-by: Jens Axboe

block: enable by default support for large devices and files on 32-bit archs

2009-04-28T05:37:33+00:00

Enable by default support for large devices and files (CONFIG_LBD):

- With 1TB disks being a commodity hardware it is quite easy to hit 2TB
  limitation while building RAIDs etc. and many distros have been using
  CONFIG_LBD=y by default already (at least Fedora 10 and openSUSE 11.1).

- This should also prevent a subtle ext4 filesystem compatibility issue:
  mke2fs.ext4 defaults to creating filesystems with huge_files feature
  enabled and such filesystems cannot be later mounted read-write on
  machines with CONFIG_LBD=n (it should be quite easy to hit this issue
  when trying to use filesystem created using distro kernel on system
  running the self-build kernel, think about USB disk enclosures & co.).

While at it:

- Clarify config option help text w.r.t. mounting ext4 filesystems
  (they can be mounted with CONFIG_LBD=n but in the read-only mode).

Cc: "Theodore Ts'o" 
Signed-off-by: Bartlomiej Zolnierkiewicz 
Signed-off-by: Jens Axboe

tracing/blktrace: move the tracing file to kernel/trace

2009-02-09T09:51:02+00:00

Impact: cleanup

Move blktrace.c to kernel/trace, also move its config entry.

Signed-off-by: Frederic Weisbecker 
Acked-by: Arnaldo Carvalho de Melo 
Acked-by: Jens Axboe 
Signed-off-by: Ingo Molnar

blktrace: the ftrace interface needs CONFIG_TRACING

2009-01-27T13:30:36+00:00

Impact: build fix

Also mention in the help text that blktrace now can be used using
the ftrace interface.

Reported-by: Ingo Molnar 
Signed-off-by: Arnaldo Carvalho de Melo 
Signed-off-by: Ingo Molnar

block: Add Kconfig help which notes that ext4 needs CONFIG_LBD

2009-01-06T20:16:33+00:00

Signed-off-by: "Theodore Ts'o" 
Cc: Jens Axboe

Get rid of CONFIG_LSF

2008-12-29T07:29:51+00:00

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 
Signed-off-by: Jens Axboe