Re: [RFC] fsblock

[Christoph Hellwig]

On Sat, Jun 30, 2007 at 07:10:27AM -0400, Jeff Garzik wrote:
> >Not really, the current behaviour is a bug.  And it's not actually buffer
> >layer specific - XFS now has a fix for that bug and it's generic enough
> >that everyone could use it.
> 
> I'm not sure I follow.  If you require block allocation at mmap(2) time, 
> rather than when a page is actually dirtied, you are denying userspace 
> the ability to do sparse files with mmap.
> 
> A quick Google readily turns up people who have built upon the 
> mmap-sparse-file assumption, and I don't think we want to break those 
> assumptions as a "bug fix."
> 
> Where is the bug?

It's not mmap time but page dirtying time.  Currently the default behaviour
is not to allocate at page dirtying time but rather at writeout time in
some scenarious.

(and s/allocation/reservation/ applies for delalloc of course)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/