From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: [RFC 0/13] extents and 48bit ext3 Date: Fri, 9 Jun 2006 16:06:56 -0700 (PDT) Message-ID: References: <448992EB.5070405@garzik.org> <4489A7ED.8070007@garzik.org> <20060609195750.GD10524@thunk.org> <20060609203803.GF3574@ca-server1.us.oracle.com> <20060609205036.GI7420@redhat.com> <4489E8EF.5020508@garzik.org> <20060609225604.GK5964@schatzie.adilger.int> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Andrew Morton , Theodore Tso , Jeff Garzik , ext2-devel , linux-kernel@vger.kernel.org, cmm@us.ibm.com, linux-fsdevel@vger.kernel.org, Dave Jones , Alex Tomas Return-path: To: Andreas Dilger In-Reply-To: <20060609225604.GK5964@schatzie.adilger.int> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ext2-devel-bounces@lists.sourceforge.net Errors-To: ext2-devel-bounces@lists.sourceforge.net List-Id: linux-fsdevel.vger.kernel.org On Fri, 9 Jun 2006, Andreas Dilger wrote: > > Umm, and how is this fundamentally different from similar code paths in > the VFS (e.g. O_DIRECT vs regular writes)? That's a great argument. You're arguing that your thing is good by pointing to a known disaster area and saying "but that other thing does it too, so it must be good". O_DIRECT is a piece of crap, and I'm still sorry that I didn't push back enough on it. And I _did_ push back on it. But I finally was worn down. And yes, part of the problem is exactly that it uses _almost_ the same paths, but not quite. Oh, well. Linus