> >> > BTW. Is it possible to bypass the shared block in the > >> 'ram_find_and_save_block'? > >> > I mean no to check if a page is dirty for a shared block, it may > >> > make things > >> faster. > >> > >> Nice spotted. That would make things faster. But once there we > >> could split the bitmap by ramblock, and the migration_dirty_pages > >> also per block, that would make all the searchs faster, and > >> adding/removing blocks of ram much easier. If we enter optimizing > >> that function, we could really do much better that the "again" parameter > that we have right now. > >> > >> Later, Juan. > > > This patch focuses on the core thing: adding the ability to bypass migrating > the memory. > I don't want to add further optimization for it now. > I hope this patch merged solo and earlier. > optimization patches can be sent after this patch accepted. >
Will you send a v3? Liang
