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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
