On Thu, Jun 2, 2011 at 11:01 PM, Prasad Joshi <[email protected]> wrote: > There is not much difference with sequential character operations are > performed, the code with caching performed better by small margin. The caching > code performance raised by 18% to 24% with sequential block output and by 44% > for sequentail block input. Which is understandable as the Level2 table will > always be cached after a write operation. Random seek operation worked slower > with caching code.
Btw, please mention how much slower random seeks got in the next version of the patch - unless you're able to make the slowdown go away, of course. ;-) -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
