mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ohyama_sec@ariel-networks.com
To: linux-kernel@vger.kernel.org
Subject: Question : internal processing of block I/O queue
Date: Wed, 22 Apr 2009 23:50:50 +0900 (JST)	[thread overview]
Message-ID: <20090422145050.C00333780DD@ns.ariel-networks.com> (raw)

From: Hiroyasu OHYAMA

I'm a student of Japan, and I diddle the Linux for joyment.
Could I ask you a question about block I/O.

The question is that "Does The linux block I/O processing follow a first-in first-out order"

Now, I'm making layer under low level filesystem. And I wonna make it work as Cache of data like page cache.
I could understood if I emit block I/O request with submit_bio(), the kernel delay it, and I could notice the result by .bi_end_io() method that I set.

But I have something on my mind. "Does the kernel assure the order of block I/O ?"

Once I issue a block I/O request to common I/O layer, the I/O processing is delayed. And the actual block I/O processing is executed by kernel thread.
So user who commit block I/O never have to mind the sequence of delayed block I/O requests.
But I want to know that "The block I/O processing executed first is executed earlient, or may not".

If a I/O request issued back is issued earlier than before, I have to protect the target block that is issued block I/O request.

Could you please give me the actuall operation of block I/O component, that is "It may happen, or not".

Thank you in advance.

             reply	other threads:[~2009-04-22 15:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 14:50 ohyama_sec [this message]
2009-04-22 16:17 ` Corrado Zoccolo

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=20090422145050.C00333780DD@ns.ariel-networks.com \
    --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®