From: Shawn Lin <shawn.lin@rock-chips.com>
To: Sharp.Xia@mediatek.com
Cc: shawn.lin@rock-chips.com,
angelogioacchino.delregno@collabora.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-mmc@vger.kernel.org, matthias.bgg@gmail.com,
ulf.hansson@linaro.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH 1/1] mmc: Set optimal I/O size when mmc_setip_queue
Date: Mon, 28 Aug 2023 10:27:34 +0800 [thread overview]
Message-ID: <95e9525e-3101-4433-27e2-cd69f254af1c@rock-chips.com> (raw)
In-Reply-To: <20230826162635.617-1-Sharp.Xia@mediatek.com>
Hi Sharp
On 2023/8/27 0:26, Sharp.Xia@mediatek.com wrote:
> On Fri, 2023-08-25 at 17:17 +0800, Shawn Lin wrote:
>>
>>
After more testing, most of my platforms which runs at HS400/HS200 mode
shows nearly no differences with the readahead ranging from 128 to 1024.
Yet just a board shows a performance drop now. Highly suspect it's eMMC
chip depends. I would recommand leave it to the BSP guys to decide which
readahead value is best for their usage.
>
> I tested with RK3568 and sdhci-of-dwcmshc.c driver, the performance improved by 2~3%.
>
> Before:
> root@OpenWrt:/mnt/mmcblk0p3# time dd if=test.img of=/dev/null
> 2097152+0 records in
> 2097152+0 records out
> real 0m 6.01s
> user 0m 0.84s
> sys 0m 2.89s
> root@OpenWrt:/mnt/mmcblk0p3# cat /sys/block/mmcblk0/queue/read_ahead_kb
> 128
>
> After:
> root@OpenWrt:/mnt/mmcblk0p3# echo 3 > /proc/sys/vm/drop_caches
> root@OpenWrt:/mnt/mmcblk0p3# time dd if=test.img of=/dev/null
> 2097152+0 records in
> 2097152+0 records out
> real 0m 5.86s
> user 0m 1.04s
> sys 0m 3.18s
> root@OpenWrt:/mnt/mmcblk0p3# cat /sys/block/mmcblk0/queue/read_ahead_kb
> 1024
>
> root@OpenWrt:/sys/kernel/debug/mmc0# cat ios
> clock: 200000000 Hz
> actual clock: 200000000 Hz
> vdd: 18 (3.0 ~ 3.1 V)
> bus mode: 2 (push-pull)
> chip select: 0 (don't care)
> power mode: 2 (on)
> bus width: 3 (8 bits)
> timing spec: 9 (mmc HS200)
> signal voltage: 1 (1.80 V)
> driver type: 0 (driver type B)
>
next prev parent reply other threads:[~2023-08-28 2:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 2:28 [PATCH 1/1] mmc: Set optimal I/O size when mmc_setip_queue Sharp.Xia
2023-08-24 10:55 ` Ulf Hansson
2023-08-25 7:10 ` Sharp Xia (夏宇彬)
2023-08-25 8:11 ` Shawn Lin
2023-08-25 8:39 ` Sharp.Xia
2023-08-25 9:17 ` Shawn Lin
2023-08-26 16:26 ` Sharp.Xia
2023-08-28 2:27 ` Shawn Lin [this message]
2023-08-28 9:04 ` Ulf Hansson
2023-08-25 12:23 ` Wenchao Chen
2023-08-26 16:54 ` Sharp.Xia
2023-08-25 7:25 ` Sharp.Xia
2023-08-25 7:26 ` Sharp.Xia
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=95e9525e-3101-4433-27e2-cd69f254af1c@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=Sharp.Xia@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=wsd_upstream@mediatek.com \
/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