All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 8 Aug 2012 13:37:22 +0300	[thread overview]
Message-ID: <004101cd7551$cd269130$6773b390$@codeaurora.org> (raw)
In-Reply-To: <502214E8.7070603@samsung.com>

Hi Chung

> Hi
> 
> I tested with this patch on my board.
> But i didn't get any performance benefit.
> Which benchmark did you use?

As I already mentioned I used lmdd. The results I published were collected using the bellow command run in parallel:
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

With lmdd we did see great improvement both in throughput and in read latency:
CFQ:	     READ  20.81 MB/sec,    WRITE  15.23 MB/sec   Worst case READ latency 230 msec     Worst case write latency   9370   msec
ROW:         READ  27.75 MB/sec      WRITE  15.34 MB/sec   Worst case READ latency   85 msec     Worst case write latency   12025 msec

ROW can be configured to perform at ~34 MB/sec throughput in the above scenario but in this configuration worst case write latency increases to ~13 sec.

> And sometime this scheduler didn't work well read/write operation.
> (i didn't know exactly what problem.)

This may be. We're still working on testing the scheduler and improving it. It's not yet totally "bug free". I've uploaded the code as RFC. 

> 
> 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
> 

My environment is similar except the host controller which is msm-sdcc. 
Could you please give me the exact iozone command you used? I'll replay it on my setup.

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.

  reply	other threads:[~2012-08-08 10:37 UTC|newest]

Thread overview: 19+ 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   ` Tatyana Brokhman
2012-08-05 11:30 ` [RFC/PATCH 2/2] block: Adding ROW scheduling algorithm Tatyana Brokhman
2012-08-05 11:30   ` Tatyana Brokhman
2012-08-06 16:35   ` Jeff Moyer
2012-08-06 16:35     ` Jeff Moyer
2012-08-07 11:28     ` Tanya Brokhman
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-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 [this message]
2012-08-08 11:57     ` Jaehoon Chung
2012-08-09  5:06   ` Tanya Brokhman
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='004101cd7551$cd269130$6773b390$@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 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.