From: Linus Torvalds Subject: Re: [PATCH] direct-IO API change Date: Fri, 4 Oct 2002 16:23:02 -0700 (PDT) Sender: nfs-admin@lists.sourceforge.net Message-ID: References: <3D9E1847.F6DDA3AE@digeo.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Chuck Lever , Linux Kernel Mailing List , Linux NFS List Return-path: Received: from neon-gw-l3.transmeta.com ([63.209.4.196] helo=neon-gw.transmeta.com) by usw-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 17xbl8-0000yv-00 for ; Fri, 04 Oct 2002 16:21:26 -0700 To: Andrew Morton In-Reply-To: <3D9E1847.F6DDA3AE@digeo.com> Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: 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. 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? Linus ------------------------------------------------------- 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