linux-kernel - Re: Ext3 vs NTFS performance

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	02 May 2007 20:40:35 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Theodore Tso <tytso@....edu>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Cabot, Mason B" <mason.b.cabot@...el.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Ext3 vs NTFS performance

Theodore Tso <tytso@....edu> writes:

> On Wed, May 02, 2007 at 02:21:40PM +0200, Andi Kleen wrote:
> > Andrew Morton <akpm@...ux-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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/