From: Jan Engelhardt <jengelh@inai.de>
To: Tatyana Brokhman <tlinder@codeaurora.org>
Cc: axboe@kernel.dk, Jeff Moyer <jmoyer@redhat.com>,
linux-arm-msm@vger.kernel.org,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/PATCH 2/2] block: Adding ROW scheduling algorithm
Date: Fri, 21 Sep 2012 06:35:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.01.1209210631060.13993@nerf07.vanv.qr> (raw)
In-Reply-To: <alpine.LNX.2.01.1209190718030.29967@nerf07.vanv.qr>
On Wednesday 2012-09-19 07:29, Jan Engelhardt wrote:
>On Monday 2012-08-06 18:35, Jeff Moyer wrote:
>>Tatyana Brokhman 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.
There seems to a bug with ROW. After about 43 hours of continued
operation, programs (./configure was what I ran at the time this
happened) first become slow, then got stuck in D state within a
minute. Ctrl-C/Z worked at first, soon not, then these messages
appeared in dmesg.
[319952.630605] row: forced dispatching is broken (nr_sorted=17), please report
this
[319952.631174] row: forced dispatching is broken (nr_sorted=17), please report
this
next prev parent reply other threads:[~2012-09-21 4:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1344166241-18708-1-git-send-email-tlinder@codeaurora.org>
2012-08-05 11:30 ` [RFC/PATCH 1/2] block: Expose kblock_schedule_delayed_work() Tatyana Brokhman
2012-08-05 11:30 ` [RFC/PATCH 2/2] block: Adding ROW scheduling algorithm Tatyana Brokhman
2012-08-06 16:35 ` Jeff Moyer
2012-08-07 11:28 ` Tanya Brokhman
2012-09-19 5:29 ` Jan Engelhardt
2012-09-21 4:35 ` Jan Engelhardt [this message]
2012-09-21 4:58 ` 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=alpine.LNX.2.01.1209210631060.13993@nerf07.vanv.qr \
--to=jengelh@inai.de \
--cc=axboe@kernel.dk \
--cc=jmoyer@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®