All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Linus Torvalds <torvalds@transmeta.com>,
	Badari Pulavarty <pbadari@us.ibm.com>,
	Janet Morgan <janetmor@us.ibm.com>
Cc: Chuck Lever <cel@citi.umich.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux NFS List <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] direct-IO API change
Date: Fri, 04 Oct 2002 16:35:03 -0700	[thread overview]
Message-ID: <3D9E25A7.B3E13D8@digeo.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210041621170.2526-100000@home.transmeta.com

Linus Torvalds wrote:
> 
> On Fri, 4 Oct 2002, Andrew Morton wrote:
> >
> > Because the file handle which we have is for /dev/raw/raw0,
> > not for /dev/hda1.
> >
> > The raw driver binds to major/minor, not a file*.  I considered
> > changing that (change userspace to pass the open fd).  But didn't.
> 
> Ok. I'd really rather have a cleaner internal API and break the raw driver
> for a while, than have a silly API just because the raw driver uses it.

OK - bust it.

> Especially since I thought that O_DIRECT on the regular file (or block
> device) performed about as well as raw does anyway these days? Or is that
> just one of my LSD-induced flashbacks?
> 

Now we're not holding i_sem for O_DIRECT writes to blockdevs,
I don't think the raw driver offers any advantages at all.  It's
a compatibility thing to save people from having to add "|O_DIRECT" to
their source and then typing `ln -s /dev/hda1 /dev/raw/raw0'.

I think we can probably delete the raw driver.  But I've Cc'ed Janet
and Badari to find out why that's wrong.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@digeo.com>
To: Linus Torvalds <torvalds@transmeta.com>,
	Badari Pulavarty <pbadari@us.ibm.com>,
	Janet Morgan <janetmor@us.ibm.com>
Cc: Chuck Lever <cel@citi.umich.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux NFS List <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] direct-IO API change
Date: Fri, 04 Oct 2002 16:35:03 -0700	[thread overview]
Message-ID: <3D9E25A7.B3E13D8@digeo.com> (raw)
In-Reply-To: Pine.LNX.4.44.0210041621170.2526-100000@home.transmeta.com

Linus Torvalds wrote:
> 
> On Fri, 4 Oct 2002, Andrew Morton wrote:
> >
> > Because the file handle which we have is for /dev/raw/raw0,
> > not for /dev/hda1.
> >
> > The raw driver binds to major/minor, not a file*.  I considered
> > changing that (change userspace to pass the open fd).  But didn't.
> 
> Ok. I'd really rather have a cleaner internal API and break the raw driver
> for a while, than have a silly API just because the raw driver uses it.

OK - bust it.

> Especially since I thought that O_DIRECT on the regular file (or block
> device) performed about as well as raw does anyway these days? Or is that
> just one of my LSD-induced flashbacks?
> 

Now we're not holding i_sem for O_DIRECT writes to blockdevs,
I don't think the raw driver offers any advantages at all.  It's
a compatibility thing to save people from having to add "|O_DIRECT" to
their source and then typing `ln -s /dev/hda1 /dev/raw/raw0'.

I think we can probably delete the raw driver.  But I've Cc'ed Janet
and Badari to find out why that's wrong.

  reply	other threads:[~2002-10-04 23:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 22:10 [PATCH] direct-IO API change Chuck Lever
2002-10-04 22:25 ` Linus Torvalds
2002-10-04 22:37   ` Andrew Morton
2002-10-04 23:23     ` Linus Torvalds
2002-10-04 23:23       ` Linus Torvalds
2002-10-04 23:35       ` Andrew Morton [this message]
2002-10-04 23:35         ` Andrew Morton
2002-10-04 23:44         ` Linus Torvalds
2002-10-04 23:44           ` Linus Torvalds
2002-10-04 23:56           ` Badari Pulavarty
2002-10-04 23:56             ` Badari Pulavarty
2002-10-05  0:11             ` Linus Torvalds
2002-10-05  0:11               ` Linus Torvalds
2002-10-08 13:33       ` Terje Eggestad
2002-10-08 13:33         ` Terje Eggestad
     [not found]     ` <Pine.LNX.4.44.0210041621170.2526-100000@home.transmeta.com >
2002-10-05  9:49       ` Lincoln Dale
2002-10-05  9:49         ` Lincoln Dale
2002-10-05 19:34         ` Andrew Morton

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=3D9E25A7.B3E13D8@digeo.com \
    --to=akpm@digeo.com \
    --cc=cel@citi.umich.edu \
    --cc=janetmor@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=pbadari@us.ibm.com \
    --cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.