[Ovirt-devel] [PATCH node] Changed max swap size to allow for overcommitting.

Dor Laor dlaor at redhat.com
Wed Jan 14 10:41:57 UTC 2009


Alan Pevec wrote:
> On Tue, Jan 13, 2009 at 11:33 PM, Darryl L. Pierce <dpierce at redhat.com 
> <mailto:dpierce at redhat.com>> wrote:
>
>     If the ovirt_overcommit kernel argument is passed, the value supplied
>     will override the default value, which is 2GB.
>
>
> nack - that's too easy :)
>
> lemme try to explain what I had in mind:
> parameter should accept the overcommit ratio as its value and not max. 
> size in MB - otherwise admin needs to adjust it for different machines
>
> ovirt_overcommit=N
> means swap area is set to N * MEM_SIZE
Can it be N*MEM_SIZE + the values from the table below?
This way you retain swap memory for the VMs and additional swap for the 
host.
>
> default N is 2, in case parameter is not present
Make sure N is not an int. The current solidIce default is 150%.
For 150% N should be 0.5 since the 100% is in the RAM.
> special case N=0, means overcommit is not used and swap area is set to 
> min. required size from the table in 
> http://kbase.redhat.com/faq/docs/DOC-15252
>
> MEM_SIZE    SWAP_SIZE
>
> <=4GB           2GB
>
> 4GB to 16GB  4GB
>
> 16GB to 64GB  8GB
>
> 64GB to 256GB  16GB
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ovirt-devel mailing list
> Ovirt-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/ovirt-devel
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20090114/45cc2aa0/attachment.htm>


More information about the ovirt-devel mailing list