mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hiroyasu OHYAMA <ohyama_sec@ariel-networks.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] (Documentation) append more detail explanation to the I/O scheduler API.
Date: Sun, 22 Nov 2009 21:18:02 +0900	[thread overview]
Message-ID: <20091122121802.GA4646@ns.ariel-networksc.om> (raw)

 From: Hiroyasu OHYAMA

 Signed-off-by: Hiroyasu OHYAMA <ohyama_sec@ariel-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



             reply	other threads:[~2009-11-22 12:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22 12:18 Hiroyasu OHYAMA [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-11-21  5:16 Hiroyasu OHYAMA

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091122121802.GA4646@ns.ariel-networksc.om \
    --to=ohyama_sec@ariel-networks.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®