From: カオ ミン ヒェップ <cm-hiep@jinso.co.jp>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/5] arm: shmobile: Lager Add USB and SATA support
Date: Thu, 11 Sep 2014 11:26:18 +0000 [thread overview]
Message-ID: <541186DA.1030905@jinso.co.jp> (raw)
In-Reply-To: <1387370660-20481-1-git-send-email-valentine.barshak@cogentembedded.com>
Hi Khiem-san
> It seems SATA performance (write speed) is degraded after CPUFreq is enabled
> (even performance governor is selected).
>
> Base on your test result so far:
> T1 Upstream-v3.16-rc5: 66 MB/s
> T2 v3.17-rc2 (CPUFreq disabled): ~ 66 MB/s
> T3 v3.17-rc2 (CPUFreq enable / on-demand governor): 42.61MB/s
> T4 v3.17-rc2 (CPUFreq disabled / performance governor ): 58.3MB/s
>
> The diff between T2 and T4 is ~8 MB/s (or 8% of 66 MB/s).
> I guess we should try to find the cause of this regression.
> (I wonder similar phenomenon occurs in backport version ...)
>
> (I added Inami-san, CPUFreq developer for his info.)
Have some miss in my way of the report yesterday.
As yesterday results, T2 v3.17-rc2 (CPUFreq disabled) should be
(367MB/(5.3s+1.0s)) ->58.2MB/s
Here is yesterday's report:
> As you pointed out, I changed "CONFIG_CPU_FREQ=y" to
"CONFIG_CPU_FREQ is not set" on uptream-v3.17-rc2 ,
(snip)
>root@linaro-nano:~# dd if=/dev/urandom of=/tmp/file-350mb bs=1M count50
>350+0 records in
>350+0 records out
>367001600 bytes (367 MB) copied, 90.2065 s, 4.1 MB/s
>root@linaro-nano:~# time cp /tmp/file-350mb /mnt/file; time umount /mnt/
>real 0m5.386s
>user 0m0.010s
>sys 0m5.200s
>real 0m1.078s
>user 0m0.020s
>sys 0m0.510s
And I have just re-confirmed T1 (Upstream-v3.16-rc5),
On upstream-v3.16-rc5 SATA's writing speed should be 55.6MB/s as below.
There is no uniformity in the speed calculation of SATA in our test team.
That 66MB/s only is result of copy to SATA-HDD without umount the device
before finish.
Sorry for the inconvenience.
Here is the test results of v3.16-rc5:
root@linaro-nano:~# uname -a
Linux linaro-nano 3.16.0-rc5 #4 SMP Thu Sep 11 20:01:58 JST 2014 armv7l
armv7l ax
root@linaro-nano:~# mount -t tmpfs -o size@0m tmpfs /tmp
root@linaro-nano:~# dd if=/dev/urandom of=/tmp/file-350mb bs=1M count50
350+0 records in
350+0 records out
367001600 bytes (367 MB) copied, 115.374 s, 3.2 MB/s
root@linaro-nano:~# mount /dev/sda1 /mnt/sata/
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda1): using internal journal
EXT3-fs (sda1): mounted filesystem with ordered data mode
root@linaro-nano:~# rm /mnt/sata/file-350mb
root@linaro-nano:~# time cp /tmp/file-350mb /mnt/sata/; time umount
/mnt/sata/
real 0m5.473s
user 0m0.020s
sys 0m5.430s
real 0m1.149s
user 0m0.000s
sys 0m0.510s
Speed: 55.6MB/s
>>
>> Thank you!
>> Cao Minh Hiep.
next prev parent reply other threads:[~2014-09-11 11:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 12:44 [PATCH 0/5] arm: shmobile: Lager Add USB and SATA support Valentine Barshak
2013-12-19 10:09 ` Magnus Damm
2013-12-19 13:02 ` Valentine
2013-12-19 17:56 ` Valentine
2013-12-20 14:07 ` Valentine
2014-09-10 1:21 ` Ryusuke Sakato
2014-09-10 5:18 ` カオ ミン ヒェップ
2014-09-10 7:15 ` Ryusuke Sakato
2014-09-10 9:16 ` カオ ミン ヒェップ
2014-09-10 9:32 ` Khiem Nguyen
2014-09-11 9:35 ` カオ ミン ヒェップ
2014-09-11 10:20 ` Khiem Nguyen
2014-09-11 11:26 ` カオ ミン ヒェップ [this message]
2014-09-12 0:39 ` Khiem Nguyen
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=541186DA.1030905@jinso.co.jp \
--to=cm-hiep@jinso.co.jp \
--cc=linux-sh@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.