kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: gauravmahajan2007@gmail.com (Gaurav Mahajan)
To: kernelnewbies@lists.kernelnewbies.org
Subject: A doubt regarding submit_bio()
Date: Tue, 28 Dec 2010 00:55:12 +0530	[thread overview]
Message-ID: <AANLkTi=nQZDKJqjw3iaKEr3FeLxNxrKq0kSRcAZV4YFL@mail.gmail.com> (raw)

Hello all,

I am working on a operation in which I need to assure the order of
bio_end_io() functions.
Consider the scenario,

If I submit two bio requests using submit_bio() function one after
another, then is there any guarantee that the bio_end_io() for the
bios will be invoked in the same order in which I submitted the bios?

Basically I mean to say, would the generic block layer or I/O
scheduler maintain the order of bios submitted to them?

Hoping for some help.

Regards,
Gaurav.

             reply	other threads:[~2010-12-27 19:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 19:25 Gaurav Mahajan [this message]
2010-12-29  7:20 ` A doubt regarding submit_bio() Durga Prasad

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='AANLkTi=nQZDKJqjw3iaKEr3FeLxNxrKq0kSRcAZV4YFL@mail.gmail.com' \
    --to=gauravmahajan2007@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).