Editing Page cache isolation

This page describes a new strict page cache isolation feature, which appeared in the kernel 042stab068.8 and later kernels.

The feature disables bouncing page cache pages between host and containers on physpages shortage in container. The internal reclaimer will drop cached data if container exceeded its physpages limit and pagecache isolation is turned on.

Current state can be obtained by reading the <code>/proc/bc/<id>/debug:pagecache_isolation</code> file. It is disabled by default.

The following sysctls are available:

* <code>ubc.pagecache_isolation</code> = <code>0</code>|<code>1</code>
: To turn on or off isolation for all containers

* <code>ubc.pagecache_isolation_on</code> = <<code>id</code>>
: To turn on for container <id> (write only)

* <code>ubc.pagecache_isolation_off</code> = <<code>id</code>>
: To turn off for container <id> (write only)

[[Category: HOWTO]]
[[Category: Kernel]]
@@ Line 1: / Line 1: @@
-{{Warning|This article describes legacy version of OpenVZ (version 6).
+This page describes a new strict page cache isolation feature, which appeared in the kernel 042stab068.8 and later kernels.
-This feature is absent in OpenVZ 7, similar feature in OpenVZ 7 is called '''tcache'''.}}
-This page describes a new '''strict page cache isolation''' feature, which appeared in the kernel 2.6.32-042stab068.8.
 The feature disables bouncing page cache pages between host and containers on physpages shortage in container. The internal reclaimer will drop cached data if container exceeded its physpages limit and pagecache isolation is turned on.