From: Chris Ball <cjb@laptop.org>
To: Manoj Iyer <manoj.iyer@canonical.com>
Cc: linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org,
matsumur@nts.ricoh.co.jp, linux-pci@vger.kernel.org,
linux-mmc@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] mmc: Added quirks for Ricoh 1180:e823 lower base clock frequency
Date: Tue, 12 Jul 2011 13:30:42 -0400 [thread overview]
Message-ID: <m2ei1v76f1.fsf@bob.laptop.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1107121123140.1767@lazy> (Manoj Iyer's message of "Tue, 12 Jul 2011 12:09:10 -0500 (CDT)")
Hi,
On Tue, Jul 12 2011, Manoj Iyer wrote:
> btw only the 1st write was slower, subsequent writes looks ok.
> [..]
> I have attached the output of flashbench and the time test to
>
> http://launchpad.net/bugs/773524
> [..]
> == Finding the number of open erase blocks ==
> u@u:~/flash/flashbench$ sudo ./flashbench -O --erasesize=$[4 * 1024 *
> 1024] --blocksize=$[256 * 1024] /dev/mmcblk0 --open-au-nr=2
> 4MiB 6.36M/s
> 2MiB 6.24M/s
> 1MiB 6.17M/s
> 512KiB 6.19M/s
> 256KiB 6.22M/s
> u@u:~/flash/flashbench$
> [..]
> ====== AFTER PATCH ========
> [..]
> == Finding the number of open erase blocks ==
> u@u:~/flash/flashbench$ sudo ./flashbench -O --erasesize=$[4 * 1024 *
> 1024] --blocksize=$[256 * 1024] /dev/mmcblk0 --open-au-nr=2
> [sudo] password for u:
> 4MiB 5.49M/s
> 2MiB 6.22M/s
> 1MiB 6.22M/s
> 512KiB 6.21M/s
> 256KiB 6.21M/s
> u@u:~/flash/flashbench$
That's interesting. Arnd, any idea why only the first test of the
flashbench run would be slower after the patch?
Thanks,
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2011-07-12 17:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1310419715-13254-1-git-send-email-manoj.iyer@canonical.com>
[not found] ` <1310419715-13254-2-git-send-email-manoj.iyer@canonical.com>
2011-07-11 21:53 ` [PATCH] mmc: Added quirks for Ricoh 1180:e823 lower base clock frequency Chris Ball
2011-07-11 22:55 ` Manoj Iyer
2011-07-12 16:01 ` Manoj Iyer
2011-07-12 16:20 ` Chris Ball
2011-07-12 17:09 ` Manoj Iyer
2011-07-12 17:30 ` Chris Ball [this message]
2011-07-12 18:00 ` Arnd Bergmann
2011-07-13 14:45 ` Chris Ball
2011-07-13 15:42 ` Manoj Iyer
2011-07-13 16:35 ` Arnd Bergmann
2011-07-13 16:46 ` Manoj Iyer
2011-07-13 16:55 ` Chris Ball
2011-07-13 17:02 ` Manoj Iyer
2011-07-13 17:08 ` Chris Ball
2011-07-18 20:36 ` Manoj Iyer
2011-07-18 20:40 ` Chris Ball
2011-07-18 20:47 ` Manoj Iyer
2011-07-18 21:05 ` Chris Ball
2011-07-18 21:12 ` Manoj Iyer
2011-07-19 19:43 ` Manoj Iyer
2012-11-22 0:29 ` Chris Ball
2012-11-26 16:42 ` Manoj Iyer
2012-11-26 16:57 ` Chris Ball
2011-07-13 16:50 ` Chris Ball
2011-07-13 16:54 ` Manoj Iyer
2011-07-18 23:27 ` Jesse Barnes
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=m2ei1v76f1.fsf@bob.laptop.org \
--to=cjb@laptop.org \
--cc=arnd@arndb.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manoj.iyer@canonical.com \
--cc=matsumur@nts.ricoh.co.jp \
/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).