mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Roy S.C. Ho" <scho1208@yahoo.com>
To: ptb@it.uc3m.es
Cc: linux-kernel@vger.kernel.org, scho@whizztech.com
Subject: Re: Raw access to block devices
Date: Sun, 18 Nov 2001 00:15:25 -0800 (PST)	[thread overview]
Message-ID: <20011118081525.50385.qmail@web21106.mail.yahoo.com> (raw)
In-Reply-To: <200111171615.fAHGFM027673@oboe.it.uc3m.es>

Hi Peter, thanks for your help. I found that the
control device is only for GETBIND or SETBIND. It
seems that the binded devices still have to be char
devices. Is there a way to change this?
Your help is much appreciated. Thanks.

--- "Peter T. Breuer" <ptb@it.uc3m.es> wrote:
> "A month of sundays ago Roy S.C. Ho wrote:"
> > 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
> 
> I think that's the control device. You can work out
> how to use it
> by looking at the ioctls in raw.c. But, yes, sure,
> if you get some
> "official" news on how to work it, let me know too
> and I'll use the
> info like a shot!
> 
> > simple way to maintain the block device interface
> to
> > user programs / other parts of the kernel, while
> > bypassing the buffer cache system?
> 
> Peter
> -


__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com

  reply	other threads:[~2001-11-18  8:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-17 15:44 Roy S.C. Ho
2001-11-17 16:15 ` Peter T. Breuer
2001-11-18  8:15   ` Roy S.C. Ho [this message]
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=20011118081525.50385.qmail@web21106.mail.yahoo.com \
    --to=scho1208@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ptb@it.uc3m.es \
    --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®