From: "Roy S.C. Ho" <scho1208@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: scho@whizztech.com
Subject: Raw access to block devices
Date: Sat, 17 Nov 2001 07:44:48 -0800 (PST) [thread overview]
Message-ID: <20011117154448.97910.qmail@web21101.mail.yahoo.com> (raw)
Dear all,
I would like to write a driver for a block device that
is better to be accessed directly without going
through the buffer cache. I read the source code raw.c
and learnt that linux does have raw I/O support.
However, it seems to me that the support only provides
a character device interface to users. Is there a
simple way to maintain the block device interface to
user programs / other parts of the kernel, while
bypassing the buffer cache system?
Since struct block_device_operations does not include
read or write operations, I have considered to
redirect the function pointers in filp->f_op to my own
routines when the device is opened. Is this an
appropriate solution?
Thank you very much. And please kindly correct me if I
am wrong.
Regards,
Roy Ho
__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com
next reply other threads:[~2001-11-17 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-17 15:44 Roy S.C. Ho [this message]
2001-11-17 16:15 ` Peter T. Breuer
2001-11-18 8:15 ` Roy S.C. Ho
2001-11-18 8:39 ` Peter T. Breuer
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=20011117154448.97910.qmail@web21101.mail.yahoo.com \
--to=scho1208@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scho@whizztech.com \
/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®