Re: Is there a "make hole" (truncate in middle) syscall?

[Jörn Engel]

On Mon, 15 December 2003 05:52:22 -0600, Rob Landley wrote:
> 
> The earlier suggestion I was disagreeing with would automatically create holes 
> in any file that wrote a sufficiently large range of zero bytes.  Hence the 
> cache poisoning and general defeating the purpose of DMA and such.  Neither 
> truncate, nor a punch syscall, would mess with the normal "write" path 
> (beyond locking so write and truncate/punch didn't stomp each other).

And the suggestor remains convinced that this is a good idea.  It
would be perfectly ok to defer actually looking at the data to later,
move that functionality to a journald or gcd or so, but the principle
mains unchanged.

Jörn

-- 
And spam is a useful source of entropy for /dev/random too!
-- Jasmine Strong
-
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/