To: Theodore Tso <tytso@mit.edu>
Cc: Andi Kleen <andi@firstfloor.org>,
       Andrew Morton <akpm@linux-foundation.org>,
       "Cabot, Mason B" <mason.b.cabot@intel.com>,
       linux-kernel@vger.kernel.org
Subject: Re: Ext3 vs NTFS performance
References: <B326D0531AF1BA48B4C1E9EBA239A050033DB3C1@scsmsx412.amr.corp.intel.com>
	<20070501142325.09c294bd.akpm@linux-foundation.org>
	<p73slafxvor.fsf@bingen.suse.de> <20070502160436.GA19442@thunk.org>
From: Andi Kleen <andi@firstfloor.org>
Date: 02 May 2007 20:40:35 +0200
In-Reply-To: <20070502160436.GA19442@thunk.org>
Message-ID: <p73y7k7vzks.fsf@bingen.suse.de>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1116
Lines: 20

Theodore Tso <tytso@mit.edu> writes:

> On Wed, May 02, 2007 at 02:21:40PM +0200, Andi Kleen wrote:
> > Andrew Morton <akpm@linux-foundation.org> writes:
> > > 
> > > Conceivably we could address this in the filesystem without mucking other
> > > things up.  But I'd have thought the simplest damage-control would be to
> > > detect this pattern in samba and to then use glibc's fallocate().
> > 
> > The advantage of detecting it in kernel would be that it would handle
> > Linux applications that do this (I suspect there are some) too.
> 
> Um, which applications do you suspect?  So we can hunt down those user
> space applications programmers and slap them silly?  Or rather,
> unsilly, since that there's no good reason to ever suspect that
> writing a byte every 128k would result in a good allocation layout on disk?

Anything that uses glibc fallocate() ?

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/