From: kai@gnukai.com (Kai Meyer)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Generic I/O
Date: Mon, 14 Nov 2011 12:15:14 -0700 [thread overview]
Message-ID: <4EC168C2.8090402@gnukai.com> (raw)
I'm finding it's really simple to write generic I/O functions for block
devices (via a "struct block_device") to mimic the posix read() and
write() functions (I have to supply the position, since I don't have a
fd to keep a position for me, but that's perfectly ok).
I've got a little hack that allows me to run synchronously or
asynchronously, relying on submit_bio() to create the threads for me. My
caller function has an atomic_t value that I set equal to the number of
bios I want to submit. Then I pass a pointer to that atomic_t around to
each of the bios which decrement it in the endio function for that bio.
Then the caller does this:
while(atomic_read(numbios) > 0)
msleep(1);
I'm finding the msleep(1) is a really really really long time,
relatively. It seems to work ok if I just have an empty loop, but it
also seems to me like I'm re-inventing a wheel here. Are there
mechanisms that are better suited for waiting for tasks to complete? Or
even for generic block I/O functions?
-Kai Meyer
next reply other threads:[~2011-11-14 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 19:15 Kai Meyer [this message]
2011-11-15 18:13 ` Generic I/O michi1 at michaelblizek.twilightparadox.com
2011-11-15 18:40 ` Kai Meyer
2011-11-15 19:12 ` michi1 at michaelblizek.twilightparadox.com
-- strict thread matches above, loose matches on Subject: below --
2011-10-31 16:24 generic I/O Kai Meyer
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=4EC168C2.8090402@gnukai.com \
--to=kai@gnukai.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).