From: Jeff Moyer <jmoyer@redhat.com>
To: Tatyana Brokhman <tlinder@codeaurora.org>
Cc: axboe@kernel.dk, linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
        linux-doc@vger.kernel.org (open list:DOCUMENTATION),
        linux-kernel@vger.kernel.org (open list)
Subject: Re: [RFC/PATCH 2/2] block: Adding ROW scheduling algorithm
References: <1344166241-18708-1-git-send-email-tlinder@codeaurora.org>
	<1344166241-18708-3-git-send-email-tlinder@codeaurora.org>
Date: Mon, 06 Aug 2012 12:35:19 -0400
In-Reply-To: <1344166241-18708-3-git-send-email-tlinder@codeaurora.org>
	(Tatyana Brokhman's message of "Sun, 5 Aug 2012 14:30:41 +0300")
Message-ID: <x49wr1cdlmg.fsf@segfault.boston.devel.redhat.com>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1046
Lines: 23

Tatyana Brokhman <tlinder@codeaurora.org> writes:

> This patch adds the implementation of a new scheduling algorithm - ROW.
> The policy of this algorithm is to prioritize READ requests over WRITE
> as much as possible without starving the WRITE requests.

Perhaps you could start off by describing the workload, and describing
why the existing I/O schedulers do not perform well.  Then, you could go
on to say why you feel that the existing I/O schedulers could not be
modified to perform better under your workload, and wrap the whole thing
up with some convincing performance numbers (including your testing
procedures so others could verify your work independently).

Without the above, I think you'll have a difficult time getting yet
another I/O scheduler merged into the kernel.

Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/