All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khiem Nguyen <khiem.nguyen.xt@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/5] arm: shmobile: Lager Add USB and SATA support
Date: Wed, 10 Sep 2014 09:32:31 +0000	[thread overview]
Message-ID: <54101AAF.90700@renesas.com> (raw)
In-Reply-To: <1387370660-20481-1-git-send-email-valentine.barshak@cogentembedded.com>

Hi Hiep-san, Sakato-san,

Sorry for interruption.

Could you also confirm performance of SATA driver
in case that CPUFreq uses performance governor ?

If SATA performance is degraded in that case,
I guess we still need countermeasure. 
(because CPUFreq will definitely be enabled in multi-platform defconfig.)

Thanks.

Best regards,
KHIEM Nguyen

On 9/10/2014 6:16 PM, カオ ミン ヒェップ wrote:
> Hi Sakato-san
> 
> On 09/10/2014 04:15 PM, Ryusuke Sakato wrote:
>> Hi Hiep-san,
>>
>>
>> I believe that I should unite the conditions of the performance test of "CONFIG_CPU_FREQ is not set" on Upstream-v3.16-rc5,
>>   and "CONFIG_CPU_FREQ=y" on uptream-v3.17-rc2.
>>
>>
>>> # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
>>> ondemand
>> In order that you may not be subject to the influence of cpufreq, you should change
>>   "CONFIG_CPU_FREQ is not set", or should perform the following setup.
>>
>>  echo -n performance > /sys/device/system/cpu/cpu0/cpufreq/scaling_governor
>>  echo -n performance > /sys/device/system/cpu/cpu1/cpufreq/scaling_governor
>>  echo -n performance > /sys/device/system/cpu/cpu2/cpufreq/scaling_governor
>>  echo -n performance > /sys/device/system/cpu/cpu3/cpufreq/scaling_governor
>>
> As you pointed out, I changed "CONFIG_CPU_FREQ=y" to "CONFIG_CPU_FREQ is not set" on uptream-v3.17-rc2 ,
> I saw that the writing speed on v3.17-rc2 and is same writing speed on v3.16-rc5.
> 
> # 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, 90.2065 s, 4.1 MB/s
> root@linaro-nano:~# mount /dev/sda1 /mnt/
> kjournald starting.  Commit interval 5 seconds
> EXT3-fs (sda1): using internal journal
> EXT3-fs (sda1): recovery complete
> EXT3-fs (sda1): mounted filesystem with ordered data mode
> 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
> 
> Thanks you for your help!
> 
> 
> 
> Cao Minh Hiep.
> 
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-09-10  9:32 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 [this message]
2014-09-11  9:35 ` カオ ミン ヒェップ
2014-09-11 10:20 ` Khiem Nguyen
2014-09-11 11:26 ` カオ ミン ヒェップ
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=54101AAF.90700@renesas.com \
    --to=khiem.nguyen.xt@renesas.com \
    --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.