From: Manoj Iyer <manoj.iyer@canonical.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Manoj Iyer <manoj.iyer@canonical.com>,
Chris Ball <cjb@laptop.org>,
linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org,
matsumur@nts.ricoh.co.jp, linux-pci@vger.kernel.org,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: Added quirks for Ricoh 1180:e823 lower base clock frequency
Date: Wed, 13 Jul 2011 11:46:27 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1107131144250.3174@lazy> (raw)
In-Reply-To: <201107131835.25217.arnd@arndb.de>
Chris,
Do you think that lowering the controller speed to 50Mhz in case we have a
failure is a better idea than reducing the speed for all e823 ricoh
controllers? I can send a V2 of the patch. What do you think ?
On Wed, 13 Jul 2011, Arnd Bergmann wrote:
> On Wednesday 13 July 2011, Manoj Iyer wrote:
>>
>> Chris/Arnd,
>>
>> Here is a series of test I did with the patched kernel.
>
>> == cold boot insert SD card ==
>> u@u:~/flash/flashbench$ sudo ./flashbench -O --erasesize=$[4 * 1024 *
>> 1024] --blocksize=$[256 * 1024] /dev/mmcblk0 --open-au-nr=2
>> 4MiB 4.96M/s
>> 2MiB 6.3M/s
>> 1MiB 6.23M/s
>> 512KiB 6.23M/s
>> 256KiB 6.26M/s
>
> The very first one obviously triggers a garbage collection.
> Everything after that is well within measuring accuracy around 6.25MB/s
>
>> On Wed, 13 Jul 2011, Chris Ball wrote:
>
>>>
>>> That makes sense. Do you think this explains Manoj getting a slower
>>> first file copy speed (757ms vs. 480ms) after applying his patch?
>>> (Manoj, perhaps you could retry your test without GC being needed?)
>
> Yes. For a single sample, it can easily explain differences up to 500ms.
> You have to average out file system benchmarks across a lot of files
> to be sure.
>
>>> What would we expect lowering the SD base clock frequency from 200MHz
>>> to 50MHz to do to performance theoretically?
>
> Not much. This card only has a 6MB/s write speed, which is well below
> what a 50 MHz bus can do. It mgiht be different on a fast eMMC device
> or a Sandisk Extreme Pro UHS-1 card.
>
> Arnd
>
>
--
====================
Manoj Iyer
Ubuntu/Canonical
Hardware Enablement
====================
next prev parent reply other threads:[~2011-07-13 16:46 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
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 [this message]
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=alpine.DEB.2.02.1107131144250.3174@lazy \
--to=manoj.iyer@canonical.com \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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