From: Clemens Eisserer <linuxhippy@gmail.com>
To: linux-newbie@vger.kernel.org
Subject: How to access block-devices from kernel-space?
Date: Thu, 5 Mar 2015 13:07:58 +0100 [thread overview]
Message-ID: <CAFvQSYRs31dBD2G-A-BPSmtsdRe2qw3u8Cj-D7u0okzuV6huKg@mail.gmail.com> (raw)
Hi,
I am currently working on a block-device driver which implements a
logical block device on top of a real block device.
There are several examples showing how to write a block device driver
and that seems straight-forward, however accessing the backing block
device is causing me headache.
I found the bio API to be quite complex for what I am trying to do -
the old "buffer-head" API on the other hand seems to be almost
undocumented.
Is there another/simpler way to read/write block-devices in a
synchronous manner?
What I am looking is something like the read/write syscall
functionality, however I would like to avoid using the syscall-code
for overhead reasons.
Thank you in advance, Clemens
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
reply other threads:[~2015-03-05 12:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAFvQSYRs31dBD2G-A-BPSmtsdRe2qw3u8Cj-D7u0okzuV6huKg@mail.gmail.com \
--to=linuxhippy@gmail.com \
--cc=linux-newbie@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).