From: "Tanya Brokhman" <tlinder@codeaurora.org>
To: 'Jan Engelhardt' <jengelh@inai.de>
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 07:58:19 +0300 [thread overview]
Message-ID: <003d01cd97b5$ba4e70b0$2eeb5210$@codeaurora.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1209210631060.13993@nerf07.vanv.qr>
Hi Jan
> 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
Thank you very much for reporting this!
We're now at the testing phase as well. We didn't encounter the bug you
observed but I'll look into it. Thanks again.
Thanks,
Tanya Brokhman
---
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2012-09-21 4:58 UTC|newest]
Thread overview: 14+ 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 ` [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
2012-09-21 4:58 ` Tanya Brokhman [this message]
2012-08-08 7:27 ` [RFC/PATCH 0/2] ROW scheduling Algorithm Jaehoon Chung
2012-08-08 10:37 ` 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='003d01cd97b5$ba4e70b0$2eeb5210$@codeaurora.org' \
--to=tlinder@codeaurora.org \
--cc=axboe@kernel.dk \
--cc=jengelh@inai.de \
--cc=jmoyer@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).