On Wed, May 02, 2007 at 08:40:35PM +0200, Andi Kleen wrote:
> Theodore Tso <[EMAIL PROTECTED]> writes:
>
> > On Wed, May 02, 2007 at 02:21:40PM +0200, Andi Kleen wrote:
> > > Andrew Morton <[EMAIL PROTECTED]> 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() ?
Glibc's fallocate current writes all zeros, not 1 byte every
128kbytes. And once we wire up the new sys_fallocate() support, we'll
have the right preallocation support in ext4.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
