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.
>
>
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
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
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.
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
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
Hi Jeff
First of all - thank you for your input! I think I did address at least some
of the issues you mentioned. But allow me to elaborate
> Perhaps you could start off by describing the workload, and describing why
> the existing I/O schedulers do not perform well.
In mobile devices we won't
Hi Jeff
First of all - thank you for your input! I think I did address at least some
of the issues you mentioned. But allow me to elaborate
Perhaps you could start off by describing the workload, and describing why
the existing I/O schedulers do not perform well.
In mobile devices we won't
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
Tatyana Brokhman tlin...@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
10 matches
Mail list logo
