Jamie Lokier wrote:
> 

<snip>

> What you want is to run as fast as usual, with all the nice 
> elevator and write back rules, but with writes to the disk 
> sustained until there aren't any further dirty blocks.
> 
> This strikes me as perfectly reasonable behaviour for all 
> removable media and I can see no reason why anyone argues 
> against it.  It's not like there's a performance cost to 
> simply writing your dirty data when the medium's request 
> queue empties.

This would suit me perfectly.  Is it feasible to implement
within the current architecture?  Would it require any
extensive rewriting or would the modifications be relatively
easy to develop and implement?

Thanks,
        Miles

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to