Avi Kivity wrote: > Michael Tokarev wrote: >>>> As you see, it writes 2 bytes, llseeks to THE SAME >>>> position, writes next 2 bytes and so on. This takes >>>> HUGE amount of time, and can be done, in most cases, >>>> in a single write without any seeks. [] > Any idea what is happening? Is it disk bound, or cpu bound?
Yes, see above. llseek(curpos)+write(2bytes) - try doing that for for a more-or-less large file and you'll see ;) And it seems that this slowness is here for a long time really. It's just that change in default write/cache mode made the problem very obvious. /mjt -- 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
