[RC5] Cache buffers in ram suggestion.
mmichael at TechFak.Uni-Bielefeld.DE
Fri Aug 30 18:42:22 EDT 2002
IMHO you the blocks 'cached' in RAM should not be in the buff-in nor in a
buff.somethimg. Then would have a new buff.something you had to keep it
uptodate everytime you finish a cached block.
Then someone want to store some blocks in Memory, he must take the
rist losing his work (and dnetc the lost of non-returning blocks...)
Just my 0.02 EUR
Am 30.08.02 um 10:29 schrieb James Spinks:
> Quoting dan carter <hedonist at win.co.nz>:
> > It would be nice if the client could load several hours worth of buffers
> > into ram to work on before touching the disc to put them in the out
> > buffer and load up more.
> For this too work (and I'm not poo-poo'ing it at all, I think it's a great
> suggestion), it would either have to be an option that defaulted to disabled
> (with plenty of warnings in the config screen) or the act of caching would
> somehow mark the blocks that were being cached or even move them into a
> buff.cached file leaving the buff.in file free for other clients to take from.
Ceterum censeo Microsoftem esse delendam!
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest
More information about the rc5