linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: merez@codeaurora.org
To: "S, Venkatraman" <svenkatr@ti.com>
Cc: Maya Erez <merez@codeaurora.org>,
	linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/1] block: Add test-iosched scheduler
Date: Sat, 9 Jun 2012 07:54:18 -0700 (PDT)	[thread overview]
Message-ID: <41394741acbaf5451f81382a2f31b44f.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <CANfBPZ8C7YY760yx9ATi1_UJ_itL0N+fVdxx0Lim-55SgGjbng@mail.gmail.com>


> On Thu, Jun 7, 2012 at 1:14 AM, Maya Erez <merez@codeaurora.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.
The main benefit of the test-iosched is the ability to determine the
timing of each request that is being dispatched and to put on hold the
real FS requests so that they won't affect the tests scenario.
It also allows each block device to determine pass/fail result taking into
account the expected behavior and the actual result.
The scheduler doesn't have to be changed per tests case. What made you
think it should be?
Currently we use the test-iosched to test the eMMC4.5 features (such as
BKOPs, packed commands and sanitize). I hope that after we will release
the tests later this week it will be clearer.
>
>> 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
>>
>

Thanks,
Maya Erez
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum

  reply	other threads:[~2012-06-09 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06 19:44 [PATCH v2 0/1] block: Add test-iosched scheduler Maya Erez
2012-06-06 19:44 ` [PATCH v2 1/1] " Maya Erez
2012-06-08 10:53 ` [PATCH v2 0/1] " S, Venkatraman
2012-06-09 14:54   ` merez [this message]
2012-06-11 15:36     ` S, Venkatraman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41394741acbaf5451f81382a2f31b44f.squirrel@www.codeaurora.org \
    --to=merez@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=svenkatr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).