All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Tatyana Brokhman <tlinder@codeaurora.org>
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, 08 Aug 2012 16:27:36 +0900	[thread overview]
Message-ID: <502214E8.7070603@samsung.com> (raw)
In-Reply-To: <1344166241-18708-1-git-send-email-tlinder@codeaurora.org>

Hi

I tested with this patch on my board.
But i didn't get any performance benefit.
Which benchmark did you use?
And sometime this scheduler didn't work well read/write operation.
(i didn't know exactly what problem.)

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?

Best Regards,
Jaehoon Chung

On 08/05/2012 08:30 PM, Tatyana Brokhman wrote:
> The ROW scheduling algorithm will be used in mobile devices as default
> block layer IO scheduling algorithm. ROW stands for "READ Over WRITE"
> which is the main requests dispatch policy of this algorithm.
> 
> The ROW IO scheduler was developed with the mobile devices needs in
> mind. In mobile devices we favor user experience upon everything else,
> thus we want to give READ IO requests as much priority as possible.
> In mobile devices we won’t have AS much parallel threads as on desktops.
> Usually it’s a single thread or at most 2 simultaneous working threads
> for read & write. Favoring READ requests over WRITEs decreases the READ
> latency greatly.
> 
> The main idea of the ROW scheduling policy is:
> If there are READ requests in pipe - dispatch them but don't starve
> the WRITE requests too much.
> 
> Bellow you’ll find a small comparison of ROW to existing schedulers.
> The test that was run for these measurements is parallel lmdd read and write.
> The tests were performed on:
> kernel version: 3.4
> Underline device driver: mmc
> Host controller: msm-sdcc
> Card:standard emmc NAND flash
> 
> --------------------------------------------------------------------------
>    Algorithm   |   Throughput [mb/sec]   |   Worst case Latency [msec]   |
>                |     READ    |   WRITE   |     READ      |     WRITE     |
> --------------------------------------------------------------------------
> Noop           |    12.12    |   25.18   |     4407      |      4804     |
> Deadline       |    12.02    |   24.6    |     705       |      5130     | 
> CFQ	       |    20.81    |   15.23   |     230       |      9370     |
> ROW	       |    27.75    |   15.34   |      85       |     12025     |
> -------------------------------------------------------------------------|
> 
> 
> Tatyana Brokhman (2):
>   block: Expose kblock_schedule_delayed_work()
>   block: Adding ROW scheduling algorithm
> 
>  Documentation/block/row-iosched.txt |  117 ++++++
>  block/Kconfig.iosched               |   22 ++
>  block/Makefile                      |    1 +
>  block/row-iosched.c                 |  675 +++++++++++++++++++++++++++++++++++
>  include/linux/blkdev.h              |    2 +
>  5 files changed, 817 insertions(+), 0 deletions(-)
>  create mode 100644 Documentation/block/row-iosched.txt
>  create mode 100644 block/row-iosched.c
> 

  parent reply	other threads:[~2012-08-08  7:27 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 ` Jaehoon Chung [this message]
2012-08-08 10:37   ` [RFC/PATCH 0/2] ROW scheduling Algorithm Tanya Brokhman
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=502214E8.7070603@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=tlinder@codeaurora.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.