From: greg.freemyer@gmail.com (Greg Freemyer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Conceptual questions about device driver
Date: Thu, 01 Aug 2013 23:21:48 -0400 [thread overview]
Message-ID: <4332d757-cefb-4427-a6c7-e0d0211c97ed@email.android.com> (raw)
In-Reply-To: <CAOb=_xJEY-CyspNnJPPWfmt+M5FpC4GUre2X8oh8r6Oo7c89mQ@mail.gmail.com>
neha naik <nehanaik27@gmail.com> wrote:
>Hi,
> I have some conceptual questions about device driver :
>
>1. Write order fidelity should be maintained when submitting requests
>from
>device driver to disk below.
> However, acknowledging these requests it is okay if we don't
>necessarily maintain that order, right?
I should know, but I don't think your question makes sense. Data transfers are axles immediately upon receipt by the drive. When the drive actually puts it to stable storage there is not another ack message.
I believe disk drives can typically cache a handful of tracks at a time. They can do a elevator sort internally on the tracks so the right order is not guarenteed but that has nothing to do with acks back to the driver.
>2. Also i want to understand what the device driver does say if in a
>multiple paged bio, some of the pages get written
> and some don't, we send the error in the bio. But what about the pages
>it has already written??? It can't possibly
> do anything about it, right?
I believe the entire bio is failed. The old data is considered lost and the new never written. Higher levels may retry smaller sections to see how much they can get out.
>
>Regards,
>Neha
>
Greg
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2013-08-02 3:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 20:55 Conceptual questions about device driver neha naik
2013-08-02 3:21 ` Greg Freemyer [this message]
2013-08-02 14:24 ` Valdis.Kletnieks at vt.edu
2013-08-02 5:32 ` Rajat Sharma
2013-08-02 19:56 ` Greg Freemyer
2013-08-02 21:10 ` neha naik
2013-08-02 22:33 ` Greg Freemyer
2013-08-02 5:55 ` Kumar Amit Mehta
-- strict thread matches above, loose matches on Subject: below --
2013-08-03 3:55 Rajat Sharma
2013-08-03 4:39 Rajat Sharma
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=4332d757-cefb-4427-a6c7-e0d0211c97ed@email.android.com \
--to=greg.freemyer@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).