As you pointed out, i was just replying to you instead of the list (thx for that) so heres my last message and my answer to you answer:
The problem i see is that slots are a scarce resource (i think they are limited to 8 now) and they shouldnt be wasted. There are some cases in which we could run out of slots even without having any memory holes. Sample case: 1) Create continuous memory block (1 slot used) 2) Create memory hole (3 slots used: mem - hole - mem) 3) Remove memory hole (3 slots used: mem - mem - mem) 4) Map the hole somewhere else (5 slots used: mem - hole - mem - mem - mem) 5) Remove memory hole (5 slots used: mem - mem - mem - mem - mem) With the change I propose we could be using just 1 slot in 1) and 5) and only 3 in 4). Of course the slot-merging should be done in kernel space just like in the user space example. --- In your last mail you say slots are not a scarce resource so i understand the 8 limitation could be raised to many more (maybe in the hundreds?). Anyway, each slot you create is a new structure in memory. I still think it would be better to have as few as possible, specially when the solution doesnt seem to have any counterparts. This procedure would only take cpu time when a slot gets inserted or removed and not while the vm is running so whats the problem with it? -- 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
