From owner-cvs-all@FreeBSD.ORG Fri Mar 28 02:02:12 2003 Return-Path: Delivered-To: cvs-all@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 683) id 1E0F837B401; Fri, 28 Mar 2003 02:02:12 -0800 (PST) Date: Fri, 28 Mar 2003 02:02:12 -0800 From: Eivind Eklund To: Alfred Perlstein Message-ID: <20030328020212.A62090@FreeBSD.org> References: <200303262340.h2QNegJg065498@repoman.freebsd.org> <20030327031602.C77894@FreeBSD.org> <20030327173918.GZ48996@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030327173918.GZ48996@elvis.mu.org>; from bright@mu.org on Thu, Mar 27, 2003 at 09:39:18AM -0800 X-Spam-Status: No, hits=-32.5 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_MUTT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: Tor Egge cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/conf NOTES files options src/sys/kern vfs_bio.c src/sys/ufs/ffs ffs_rawread.c ffs_vnops.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2003 10:02:13 -0000 On Thu, Mar 27, 2003 at 09:39:18AM -0800, Alfred Perlstein wrote: > * Eivind Eklund [030327 03:16] wrote: > > On Wed, Mar 26, 2003 at 03:40:42PM -0800, Tor Egge wrote: > > > tegge 2003/03/26 15:40:42 PST > > > > > > FreeBSD src repository > > > > > > Modified files: > > > sys/conf NOTES files options > > > sys/kern vfs_bio.c > > > sys/ufs/ffs ffs_vnops.c > > > Added files: > > > sys/ufs/ffs ffs_rawread.c > > > Log: > > > Add support for reading directly from file to userland buffer when the > > > O_DIRECT descriptor status flag is set and both offset and length is a > > > multiple of the physical media sector size. > > > > Why only in the O_DIRECT case? O_DIRECT is normally used to avoid caching > > effects *in order to avoid side effects of caching*, at the cost of speed. > > This patch seems to do the opposite - speed up the codepath significantly. > > > > Not that it isn't nice - it would just be even nicer to have available some > > way to just say "max speed, please". > > Actually this is what O_DIRECT was intended to be as soon as someone > got around to it. I initially thought it would be dillon, but tegge > was a pleasant suprise. :) I am not protesting that this is appropriate for O_DIRECT - I think it is a brilliant improvement for O_DIRECT :-) However, if the intent of O_DIRECT is to avoid caching in order to provide maximum speed, then the documentation is really off target. Either the docs or the code or both seems to be in need of updating. Eivind.