From: "Tanya Brokhman" <tlinder@codeaurora.org>
To: 'Jaehoon Chung' <jh80.chung@samsung.com>
Cc: axboe@kernel.dk, linux-mmc@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: RE: [RFC/PATCH 0/2] ROW scheduling Algorithm
Date: Thu, 9 Aug 2012 08:06:25 +0300 [thread overview]
Message-ID: <004201cd75ec$bb701970$32504c50$@codeaurora.org> (raw)
In-Reply-To: <502214E8.7070603@samsung.com>
Hi Chung
> The below is my environment:
> Kernel Version: linux-3.4
> Card: eMMC4.5 (50MHz DDR mode, 8-bit buswidth) Host controller : dw-
> mmc (DesignWare MMC controller) Benchmark : IOzone
>
> *CFQ Scheduler
> Read : 35MB
> Write : 17MB
>
> *ROW Scheduler
> Read : 28MB
> Write : 17MB
>
> How do you think about this result?
>
I run your cmd of iozone on my setup and got a bit different results:
CFQ scheduler:
204800 16384 27903 27248 40345 40399
READ: 40 MB/sec WRITE: 27 MB/sec
ROW scheduler:
READ: 39.6 MB/sec WRITE: 27MB/sec
As you can see the results are the same for both schedulers.
Anyway, the improvement added by ROW is in scenario of parallel read and write, which iozone doesn't do so running iozone for comparing ROW to CFQ is useless.
If it's not too difficult I would appreciate if you could run the bellow 2 commands simultaneously on your setup:
adb shell /data/lmdd if=internal of=/data/writefile bs=128k count=3000
adb shell /data/lmdd if=/data/readfile of=internal bs=128k count=3000
You'll see an improvement in throughput when using ROW over CFQ.
We have a patch that also measures latency and we saw that read latency was also improved greatly when using ROW.
Thanks,
Tanya Brokhman
---
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2012-08-09 5:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 11:30 [RFC/PATCH 0/2] ROW scheduling Algorithm Tatyana Brokhman
2012-08-05 11:30 ` [RFC/PATCH 1/2] block: Expose kblock_schedule_delayed_work() Tatyana Brokhman
2012-08-05 11:30 ` [RFC/PATCH 2/2] block: Adding ROW scheduling algorithm Tatyana Brokhman
2012-08-06 16:35 ` Jeff Moyer
2012-08-07 11:28 ` Tanya Brokhman
2012-09-19 5:29 ` Jan Engelhardt
2012-09-21 4:35 ` Jan Engelhardt
2012-09-21 4:58 ` Tanya Brokhman
2012-08-08 7:27 ` [RFC/PATCH 0/2] ROW scheduling Algorithm Jaehoon Chung
2012-08-08 10:37 ` Tanya Brokhman
2012-08-08 11:57 ` Jaehoon Chung
2012-08-09 5:06 ` Tanya Brokhman [this message]
2012-08-14 19:09 ` Jae hoon Chung
2012-08-20 8:44 ` Seungwon Jeon
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='004201cd75ec$bb701970$32504c50$@codeaurora.org' \
--to=tlinder@codeaurora.org \
--cc=axboe@kernel.dk \
--cc=jh80.chung@samsung.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mmc@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 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).