On 12/13/2011 03:44 PM, Christoffer Dall wrote: > >> > It's not really critical to have efficient reclaim here, since it > >> > happens so rarely. It just needs to do something. > >> > > >> > >> when would you trigger it - when it reaches a certain limit, or? And > >> then what, free the lot and re-allocate what's needed? > > > > The kernel triggers it based on internal pressure. It tells you how > > much pressure to apply, so you just translate it to a number of pages to > > free. > > > > > > ok, so we pick those pages at random? (perhaps trying to avoid hitting > the guest kernel at least for Linux, or...?) x86 has a sort of poorly managed LRU; it's wildly inaccurate but doesn't hurt in practice since it only triggers under severe memory pressure anyway. > > It doesn't have to be there for the merge but I recommend giving it high > > priority. At least read and understand the code so the addition will > > follow naturally. > > > will do - I will make it a Christmas activity. I was hoping to to get the ARM port as a present... -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
