[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANfBPZ8C7YY760yx9ATi1_UJ_itL0N+fVdxx0Lim-55SgGjbng@mail.gmail.com>
Date: Fri, 8 Jun 2012 16:23:21 +0530
From: "S, Venkatraman" <svenkatr@...com>
To: Maya Erez <merez@...eaurora.org>
Cc: linux-mmc@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/1] block: Add test-iosched scheduler
On Thu, Jun 7, 2012 at 1:14 AM, Maya Erez <merez@...eaurora.org> wrote:
> 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
>
I can't get the point. Isn't this possible purely from userspace using IOCTLs ?
Even otherwise, requiring to modify the scheduler for each test case
is definitely not scalable.
> Changes in v2:
> - Export test-iosched functionality to allow definition of the block device
> tests under the block device layer
> - Add registration of block device tests utilities
>
> Maya Erez (1):
> block: Add test-iosched scheduler
>
> Documentation/block/test-iosched.txt | 39 ++
> block/Kconfig.iosched | 8 +
> block/Makefile | 1 +
> block/blk-core.c | 3 +-
> block/test-iosched.c | 1025 ++++++++++++++++++++++++++++++++++
> include/linux/test-iosched.h | 218 +++++++
> 6 files changed, 1292 insertions(+), 2 deletions(-)
> create mode 100644 Documentation/block/test-iosched.txt
> create mode 100644 block/test-iosched.c
> create mode 100644 include/linux/test-iosched.h
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists