block: Add test-iosched scheduler
Subsystems (4)
cover block: Add test-iosched scheduler
The test scheduler allows testing a block device by dispatching specific requests according to the test case and declare PASS/FAIL according to the requests completion error code
Maya Erez (1):
block: Add test-iosched scheduler
Documentation/block/test-iosched.txt | 32 ++ block/Kconfig.iosched | 8 + block/Makefile | 1 + block/blk-core.c | 4 +- block/test-iosched.c | 966 ++++++++++++++++++++++++++++++++++ 5 files changed, 1010 insertions(+), 1 deletions(-) create mode 100644 Documentation/block/test-iosched.txt create mode 100644 block/test-iosched.c
Signature · 4 lines
1.7.3.3 -- Sent by a consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
PATCH 1/1 block: Add test-iosched scheduler
The test scheduler allows testing a block device by dispatching specific requests according to the test case and declare PASS/FAIL according to the requests completion error code
Signed-off-by Maya Erez <[email protected]>
--- Documentation/block/test-iosched.txt | 32 ++ block/Kconfig.iosched | 8 + block/Makefile | 1 + block/blk-core.c | 4 +- block/test-iosched.c | 966 ++++++++++++++++++++++++++++++++++ 5 files changed, 1010 insertions(+), 1 deletions(-) create mode 100644 Documentation/block/test-iosched.txt create mode 100644 block/test-iosched.c
Documentation/block/test-iosched.txt new file +32 -0
@@ -0,0 +1,32 @@ +Test IO scheduler +================== + +The test scheduler allows to test the a block device by dispatching +specific requests according to the test case and declare PASS/FAIL +according to the requests completion error code. + +Each test is exposed via debugfs and can be triggered by writing to +the debugfs file. In order to add a new test one should expose a new debugfs +file for the new test. + +The test IO scheduler includes the no-op scheduler operations, and uses +them in order to dispatch the non-test requests when no test is running. +This will allow to keep a normal FS operation in parallel to the test +capability. +The test IO sceduler keeps two different queues, one for non-test requests +(inserted by the FS) and the other for test requests. +The test IO scheduler chooses the queue for dispatch requests according to the +test state (IDLE/RUNNING). + +the test IO scheduler is compiled by default as a dynamic module and enabled +only if CONFIG_DEBUG_FS is defined. + +Selecting IO schedulers +----------------------- +Refer to Documentation/block/switching-sched.txt for information on +selecting an io scheduler on a per-device basis. + + +May 10 2012, maya Erez <[email protected]> + +
block/Kconfig.iosched +8 -0
@@ -12,6 +12,14 @@ config IOSCHED_NOOP that do their own scheduling and require only minimal assistance from the kernel. +config IOSCHED_TEST + tristate "Test I/O scheduler" + depends on DEBUG_FS + default m + ---help--- + The test I/O scheduler is duplicate of the noop scheduler with + test ability. + config IOSCHED_DEADLINE tristate "Deadline I/O scheduler" default y
block/Makefile +1 -0
@@ -15,6 +15,7 @@ obj-$(CONFIG_BLK_DEV_THROTTLING) += blk-throttle.o obj-$(CONFIG_IOSCHED_NOOP) += noop-iosched.o obj-$(CONFIG_IOSCHED_DEADLINE) += deadline-iosched.o obj-$(CONFIG_IOSCHED_CFQ) += cfq-iosched.o +obj-$(CONFIG_IOSCHED_TEST) += test-iosched.o obj-$(CONFIG_BLOCK_COMPAT) += compat_ioctl.o obj-$(CONFIG_BLK_DEV_INTEGRITY) += blk-integrity.o
block/blk-core.c +3 -1
@@ -1072,7 +1072,8 @@ struct request *blk_get_request(struct request_queue *q, int rw, gfp_t gfp_mask) {struct request *rq; -BUG_ON (rw !=READ && rw !=WRITE ); +if (unlikely (test_bit (QUEUE_FLAG_DEAD , &q->queue_flags))) +return NULL ;spin_lock_irq (q->queue_lock);if (gfp_mask & __GFP_WAIT)
@@ -1406,6 +1407,7 @@ void init_request_from_bio(struct request *req, struct bio *bio) req->ioprio =bio_prio (bio);blk_rq_bio_prep (req->q, req, bio); } +EXPORT_SYMBOL (init_request_from_bio);void blk_queue_bio (struct request_queue *q,struct bio *bio) {
block/test-iosched.c new file +966 -0
966 lines not on this page · raw message
Signature · 4 lines
1.7.3.3 -- Sent by a consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.