[lkml]   [2010]   [May]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC][PATCH 0/12] KVM, x86, ppc, asm-generic: moving dirty bitmaps to user space
On 05/10/2010 03:26 PM, Takuya Yoshikawa wrote:
>> No doubt -> get.opt is measurable, but get.opt->switch.opt is
>> problematic. Have you tried profiling to see where the time is spent
>> (well I can guess, clearing the write access from the sptes).
> Sorry but no, and I agree with your guess.
> Anyway, I want to do some profiling to confirm this guess.
> BTW, If we only think about performance improvement of time, optimized
> get(get.opt) may be enough at this stage.
> But if we consider the future expansion like using user allocated
> bitmaps,
> new API's introduced for switch.opt won't become waste, I think,
> because we
> need a structure to get and export bitmap addresses.

User allocated bitmaps have the advantage of reducing pinned memory.
However we have plenty more pinned memory allocated in memory slots, so
by itself, user allocated bitmaps don't justify this change.

Perhaps if we optimize memory slot write protection (I have some ideas
about this) we can make the performance improvement more pronounced.

error compiling committee.c: too many arguments to function

 \ /
  Last update: 2010-05-13 13:51    [W:0.122 / U:8.284 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site