From: Tanya Brokhman <tlinder@codeaurora.org>
To: jaxboe@fusionio.com
Cc: linux-arm-msm@vger.kernel.org, philippedeswert@gmail.com,
jengelh@inai.de, jh80.chung@samsung.com, tgih.jun@samsung.com,
arnd.bergmann@linaro.org, venkat@linaro.org,
linux-mmc@vger.kernel.org,
Tanya Brokhman <tlinder@codeaurora.org>
Subject: [PATCH v4 0/2] ROW scheduling Algorithm
Date: Tue, 11 Dec 2012 15:41:18 +0200 [thread overview]
Message-ID: <1355233280-25923-1-git-send-email-tlinder@codeaurora.org> (raw)
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:
Give READ requests priority over WRITE with WRITE starvation in mind
With ROW set as the scheduling algorithm we were able to:
- Reduce the worst case READ latency by 41%
- Improve the READ throughput by 63%
(All in read&write coalition scenarios)
Tanya Brokhman (1):
block: Adding ROW scheduling algorithm
Tatyana Brokhman (1):
block: compile ROW statically into the kernel
Documentation/block/row-iosched.txt | 134 +++++++
block/Kconfig.iosched | 22 ++
block/Makefile | 1 +
block/row-iosched.c | 694 +++++++++++++++++++++++++++++++++++
4 files changed, 851 insertions(+), 0 deletions(-)
create mode 100644 Documentation/block/row-iosched.txt
create mode 100644 block/row-iosched.c
--
1.7.6
--
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc.
Is a member of Code Aurora Forum, hosted by the Linux Foundation
next reply other threads:[~2012-12-11 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 13:41 Tanya Brokhman [this message]
2012-12-11 13:41 ` [PATCH v4 1/2] block: Adding ROW scheduling algorithm Tanya Brokhman
2012-12-11 13:41 ` [PATCH/RESEND v4 2/2] block: compile ROW statically into the kernel Tanya Brokhman
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=1355233280-25923-1-git-send-email-tlinder@codeaurora.org \
--to=tlinder@codeaurora.org \
--cc=arnd.bergmann@linaro.org \
--cc=jaxboe@fusionio.com \
--cc=jengelh@inai.de \
--cc=jh80.chung@samsung.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=philippedeswert@gmail.com \
--cc=tgih.jun@samsung.com \
--cc=venkat@linaro.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).