Editing VSwap testing
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | This article describes | + | This article describes 4th generation resource management, to be used in Virtuozzo 7. |
− | [originally written by xemul@] | + | {{Virtuozzo}} |
+ | |||
+ | == Introduction == | ||
+ | |||
+ | Each container is assigned RAM and SWAP limits. When a container hits | ||
+ | the RAM limit a (slow) swapout starts. When it hits the SWAP limit an | ||
+ | OOM killer is invoked for that container. | ||
+ | |||
+ | Note, that when a container hits its RAM limit, but there is enough RAM | ||
+ | on the host pages do not go to *real* swap, but instead are cached in | ||
+ | host RAM. Real swapout starts when there is no more real RAM. The same | ||
+ | is fair for FS page cache - clean cache pages are moved to the host RAM | ||
+ | instead of being dropped when a container hits its RAM limit so that no | ||
+ | pagein will happen on the next read provided there is enough free RAM on | ||
+ | the host. | ||
+ | |||
+ | The base functionality will be available in | ||
+ | |||
+ | * vzkernel-3.10.0-123.1.2.vz7.5.17 | ||
+ | * vcmmd-7.0.6 | ||
+ | |||
+ | == How to test == | ||
+ | |||
+ | [originally written by xemul@ for vswap] | ||
We need the following set of atomic tests | We need the following set of atomic tests | ||
Line 60: | Line 83: | ||
6) No leaks happen after container stop. This will be done using kmemleak - see PSBM-34183 | 6) No leaks happen after container stop. This will be done using kmemleak - see PSBM-34183 | ||
+ | |||
+ | More details will come later. | ||
[[Category: QA]] | [[Category: QA]] |