[PATCH] as-iosched: fix write batch start point

-by: Aaron Carroll <[EMAIL PROTECTED]> --- block/as-iosched.c |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/block/as-iosched.c b/block/as-iosched.c index 4513fc5..555cd6b 100644 --- a/block/as-iosched.c +++ b/block/as-iosched.c @@ -1097,7 +1097,8 @@ dispatch_

[PATCH] as-iosched: fix incorrect comments

Two comments refer to deadlines applying to reads only. This is not the case. Signed-off-by: Aaron Carroll <[EMAIL PROTECTED]> --- block/as-iosched.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/block/as-iosched.c b/block/as-iosched.c index dc715a5..4513fc5

[PATCH 0/3] Deadline iosched: Fix batching algorithm

Hi Jens, The following patches correct some issues with the deadline I/O scheduler and its batching algorithm. Patch 1 is a simple function factorisation. Patch 2 fixes a missing batch count reset, making the behaviour closer to that implied by the documentation. Patch 3 changes batch start poi

[PATCH 1/3] Deadline iosched: Factor out finding latter request

Factor finding the next request in sector-sorted order into a function deadline_latter_request. Signed-off-by: Aaron Carroll <[EMAIL PROTECTED]> --- block/deadline-iosched.c | 28 +--- 1 files changed, 17 insertions(+), 11 deletions(-) diff --git a/block/de

[PATCH 3/3] Deadline iosched: Fix batching fairness

behaviour so new batches start from the request whose expiry is earliest. Signed-off-by: Aaron Carroll <[EMAIL PROTECTED]> --- block/deadline-iosched.c | 21 +++-- 1 files changed, 7 insertions(+), 14 deletions(-) diff --git a/block/deadline-iosched.c b/block/deadline-ios

[PATCH 2/3] Deadline iosched: Reset batch for ordered requests

batches in the same data direction as old ones their full quota of requests by resetting the batch count. Signed-off-by: Aaron Carroll <[EMAIL PROTECTED]> --- block/deadline-iosched.c |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/block/deadline-iosched.c b

Re: Need information on elevator_dispatch_fn

Philipp Gruber wrote: > So I need to 'reactivate' the whole dispatching process again. The only > way to to this is probably a timer, but I couldn't get this working > since I don't understand what calls dispatch_fn. Hi Philipp, Take a look how the AS and CFQ schedulers implement this. In fact,