[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20091122121802.GA4646@ns.ariel-networksc.om>
Date: Sun, 22 Nov 2009 21:18:02 +0900
From: Hiroyasu OHYAMA <ohyama_sec@...el-networks.com>
To: linux-kernel@...r.kernel.org
Subject: [PATCH] (Documentation) append more detail explanation to the I/O scheduler API.
From: Hiroyasu OHYAMA
Signed-off-by: Hiroyasu OHYAMA <ohyama_sec@...el-networks.com>
I'm sorry, I realized that the patch which I send before is incorrect format
to send it to lkml.
So I resend it.
This patch append more detail explanation to the Documentation of API of I/O scheduler.
Thank you for reading.
---
diff --git a/Documentation/block/biodoc.txt b/Documentation/block/biodoc.txt
index 8d2158a..7c04f54 100644
--- a/Documentation/block/biodoc.txt
+++ b/Documentation/block/biodoc.txt
@@ -935,7 +935,12 @@ keeping work.
4.1. I/O scheduler API
The functions an elevator may implement are: (* are mandatory)
-elevator_merge_fn called to query requests for merge with a bio
+elevator_merge_fn called to query requests for merge with a bio. This method
+ have two following works. One is to indicate how to merge request
+ with bio from head or tail. This function doesn't merge them actually,
+ but just indicate direction for merging from head or tail, or that
+ there is no request with that bio can merge. Another work is to get
+ the request object which is merged, if the bio can do.
elevator_merge_req_fn called when two requests get merged. the one
which gets merged into the other one will be
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists