linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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,
	Tatyana Brokhman <tlinder@codeaurora.org>,
	linux-kernel@vger.kernel.org (open list)
Subject: [PATCH/RESEND v4 2/2] block: compile ROW statically into the kernel
Date: Tue, 11 Dec 2012 15:41:20 +0200	[thread overview]
Message-ID: <1355233280-25923-3-git-send-email-tlinder@codeaurora.org> (raw)
In-Reply-To: <1355233280-25923-1-git-send-email-tlinder@codeaurora.org>

From: Tatyana Brokhman <tlinder@codeaurora.org>

ROW is a new scheduling algorithm. Similar to the existing scheduling
algorithms it should be compiled to the kernel statically giving the user
the ability to switch to it without kernel recompilation.

Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>

diff --git a/block/Kconfig.iosched b/block/Kconfig.iosched
index 5a747e2..401f42d 100644
--- a/block/Kconfig.iosched
+++ b/block/Kconfig.iosched
@@ -23,6 +23,7 @@ config IOSCHED_DEADLINE
 
 config IOSCHED_ROW
 	tristate "ROW I/O scheduler"
+	default y
 	---help---
 	  The ROW I/O scheduler gives priority to READ requests over the
 	  WRITE requests when dispatching, without starving WRITE requests.
-- 
1.7.6
--
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. 
Is a member of Code Aurora Forum, hosted by the Linux Foundation

      parent reply	other threads:[~2012-12-11 13:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1355233280-25923-1-git-send-email-tlinder@codeaurora.org>
2012-12-11 13:41 ` [PATCH v4 1/2] block: Adding ROW scheduling algorithm Tanya Brokhman
2012-12-11 13:41 ` Tanya Brokhman [this message]

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-3-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-kernel@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).