OpenVZ Forum


Home » General » Support » Hitting the privvmpages limit
Re: Hitting the privvmpages limit [message #33463 is a reply to message #33462] Wed, 15 October 2008 13:56 Go to previous messageGo to previous message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Quote:


Comapring openvz vs. xen, hitting the privvmpages limit is a serious disadvantage of openvz. Even with a generous plan at many providers, you still risk hitting the limit.



1. privvmpages are not equal ro RAM pages.
2. privvmpages are equal to virtual pages.
3. virtual pages are equal to RAM + SWAP.

So, increasing privvmpages increase RAM+SWAP consumption of the VE.
Thus in can be concluded that current OpenVZ doesn't distinguish RAM and SWAP from inside the VE.

Quote:


Is there any kernel work planned or in progress to integrate container memeory with swap, so that virtual memory allocation works more like a standard kernel with swap?



Yes, of course. The development of such behavior is in progress.
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: kernel-devel 2.6.24-ovz006.2.
Next Topic: Maximum Execution
Goto Forum:
  


Current Time: Mon Oct 27 22:55:26 GMT 2025

Total time taken to generate the page: 0.23234 seconds