Re: [PATCH] VMware Balloon driver

[Jeremy Fitzhardinge <jeremy@goop.org>]

On 04/07/2010 10:30 PM, Pavel Machek wrote:
> Hi!
>
>   
>>>> 1) is not a huge amount of code, but something consistent would be  
>>>> nice.  2) is something we've been missing and is a bit of an open  
>>>> question/research project anyway.
>>>>         
>>> 3) Code that attempts to reclaim 2MB pages when possible
>>>       
>> Yes.  Ballooning in 4k units is a bit silly.
>>     
> Does it make sense to treat ballooning as a form of memory hotplug? 
>   

It has some similarities.  The main difference is granularity;
ballooning works in pages (typically 4k, but 2M probably makes more
sense), whereas memory hotplug works in DIMM-like sizes (256MB+). 
That's way too coarse for us; a domain might only have 256MB or less to
start with.

I experimented with a sort of hybrid scheme, in which I used hotplug
memory to add new struct pages to the system, but only incrementally
populated the underlying pages with the balloon driver.  That worked
pretty well, but it doesn't fit very well with how memory hotplug works
(at least when I last looked at it a couple of years ago).

    J