summaryrefslogtreecommitdiffstats
path: root/block/Kconfig
diff options
context:
space:
mode:
authorJens Axboe <axboe@suse.de>2006-03-23 20:00:26 +0100
committerJens Axboe <axboe@suse.de>2006-03-23 20:00:26 +0100
commit2056a782f8e7e65fd4bfd027506b4ce1c5e9ccd4 (patch)
treed4fe59a7ca0c110690937085548936a4535c39db /block/Kconfig
parent6dac40a7ce2483a47b54af07afebeb84131c7228 (diff)
downloadop-kernel-dev-2056a782f8e7e65fd4bfd027506b4ce1c5e9ccd4.zip
op-kernel-dev-2056a782f8e7e65fd4bfd027506b4ce1c5e9ccd4.tar.gz
[PATCH] Block queue IO tracing support (blktrace) as of 2006-03-23
Signed-off-by: Jens Axboe <axboe@suse.de>
Diffstat (limited to 'block/Kconfig')
-rw-r--r--block/Kconfig12
1 files changed, 12 insertions, 0 deletions
diff --git a/block/Kconfig b/block/Kconfig
index 377f6dd..9678364 100644
--- a/block/Kconfig
+++ b/block/Kconfig
@@ -11,4 +11,16 @@ config LBD
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"
+ 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
+
source block/Kconfig.iosched
OpenPOWER on IntegriCloud