The patch titled
as-iosched: fix write batch start point
has been added to the -mm tree. Its filename is
as-iosched-fix-write-batch-start-point.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: as-iosched: fix write batch start point
From: Aaron Carroll <[EMAIL PROTECTED]>
New write batches currently start from where the last one completed. We
have no idea where the head is after switching batches, so this makes
little sense. Instead, start the next batch from the request with the
earliest deadline in the hope that we avoid a deadline expiry later on.
Signed-off-by: Aaron Carroll <[EMAIL PROTECTED]>
Acked-by: Nick Piggin <[EMAIL PROTECTED]>
Cc: Jens Axboe <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
block/as-iosched.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN block/as-iosched.c~as-iosched-fix-write-batch-start-point
block/as-iosched.c
--- a/block/as-iosched.c~as-iosched-fix-write-batch-start-point
+++ a/block/as-iosched.c
@@ -1097,7 +1097,8 @@ dispatch_writes:
ad->batch_data_dir = REQ_ASYNC;
ad->current_write_count = ad->write_batch_count;
ad->write_batch_idled = 0;
- rq = ad->next_rq[ad->batch_data_dir];
+ rq = rq_entry_fifo(ad->fifo_list[REQ_ASYNC].next);
+ ad->last_check_fifo[REQ_ASYNC] = jiffies;
goto dispatch_request;
}
_
Patches currently in -mm which might be from [EMAIL PROTECTED] are
as-iosched-fix-write-batch-start-point.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
