From: Chris Ball <cjb@laptop.org>
To: Adrian Hunter <adrian.hunter@nokia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: mmc_test: fix performance tests that go over max_blk_count
Date: Fri, 10 Sep 2010 21:39:57 +0100 [thread overview]
Message-ID: <20100910203957.GA2966@void.printf.net> (raw)
In-Reply-To: <4C89ED69.8000301@nokia.com>
Hi Adrian,
On Fri, Sep 10, 2010 at 11:33:45AM +0300, Adrian Hunter wrote:
> From: Adrian Hunter <adrian.hunter@nokia.com>
> Date: Mon, 6 Sep 2010 12:54:06 +0300
> Subject: [PATCH] mmc_test: fix performance tests that go over max_blk_count
>
> The host controller driver limits I/O transfers to maximum
> transfer size, maximum block count, maximum segment size
> and maximum segment count. The performance tests were
> not obeying these limits which meant they would not work
> with some drivers. This patch fixes that.
>
> Signed-off-by: Adrian Hunter <adrian.hunter@nokia.com>
Thanks, applied to mmc-next.
My test machine (Dell m6300, Sandisk Extreme III 4GB) no longer BUG()s,
but it's still failing all of the transfer tests:
mmc0: Test case 22. Multi-block highmem read...
mmc0: Result: OK
mmc0: Test case 23. Best-case read performance...
mmc0: Result: Prepare stage failed! (-12)
mmc0: Test case 24. Best-case write performance...
mmc0: Result: Prepare stage failed! (-12)
mmc0: Test case 25. Best-case read performance into scattered pages...
mmc0: Result: Prepare stage failed! (-12)
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2010-09-10 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 8:33 mmc_test: fix performance tests that go over max_blk_count Adrian Hunter
2010-09-10 15:29 ` Chris Ball
2010-09-10 18:58 ` Adrian Hunter
2010-09-10 20:06 ` Chris Ball
2010-09-10 20:39 ` Chris Ball [this message]
2010-09-11 23:47 ` Chris Ball
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=20100910203957.GA2966@void.printf.net \
--to=cjb@laptop.org \
--cc=adrian.hunter@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mmc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.