On Nov 2, 2007, at 8:32 PM, Anders Andersson wrote:
On 11/2/07, Josef Drexler <[EMAIL PROTECTED]> wrote:
Hence, removing this from the default configuration would a very bad
move. If you personally are confident that you are capable of
preventing such problems on your system, including an understanding
of how they occur when using mmapped writes to sparse files, then you
may of course disable this feature. Instructions have been provided
already.
Ah. So this limit is to protect against a "broken" mmap.
It's not broken. It's working as designed, just that it can't work
when the disk is full. You get high performance with the caveat that
you need to make sure not to write more than fits on the disk. And
that's what rtorrent is doing, with a sufficiently big safety margin.
But wouldn't
this problem happen anyway if the disk buffers are larger than 512MB?
I suppose, if the filesystem has more than 500 MB pending writes, the
problem would still happen. But that's extremely unlikely unless
you're downloading on gigabit ethernet maybe. It's the size of the
unwritten data that matters, not the entire disk buffer.
--
Josef Drexler
[EMAIL PROTECTED]
_______________________________________________
Libtorrent-devel mailing list
[email protected]
http://rakshasa.no/mailman/listinfo/libtorrent-devel
