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?
- 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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
