Linux-VServer - User contributions [en]

Memory Limits

2010-05-31T13:34:31Z

Skaboom: /* Setting memory limits */

== Overview ==
A vserver kernel keeps track many resources used by each guest (context). Some of these relate to memory usage by the guest. You can place limits on these resources to prevent guests from using all the host memory and making the host unusable.

Two resources are particularly important in this regard:

* The '''Resident Set Size''' (<code>rss</code>) is the amount of pages currently present in RAM.
* The '''Address Space''' (<code>as</code>) is the total amount of memory (pages) mapped in all the processes in the context.

Both are measured in '''pages''', which are 4 kB each on Intel machines (i386). So a value of 200000 means a limit of 800,000 kB, a little less than 800 MB.

''To easily find out the page size on your host try this line and ignore the warnings''
<pre>echo 'int main () { printf ("%dKiB\n", getpagesize ()/1024); return 0; }' | gcc -xc - -o getpagesize && ./getpagesize</pre>
Each resource has a '''soft''' and a '''hard limit'''.

* If a guest exceeds the <code>rss</code> hard limit, the kernel will invoke the Out-of-Memory (OOM) killer to kill some process in the guest.
* The <code>rss</code> soft limit is shown inside the guest as the maximum available memory. If a guest exceeds the <code>rss</code> soft limit, it will get an extra "bonus" for the OOM killer (proportional to the oversize).
* If a guest exceeds the <code>as</code> hard limit, memory allocation attempts will return an error, but no process is killed.
* The <code>as</code> soft limit is not in utilized until now. In the future it may be used to penalizing guests over that limit or it could be used to force swapping on them and such ...

Bertl explained the difference between '''rss''' and '''as''' with the following example. If two processes share 100 MB of memory, then only 100 MB worth of virtual memory pages can be used at most, so the RSS use of the guest increases by 100 MB. However, two processes are using it, so the AS use increases by 200 MB.

This makes me think that limiting AS is less useful than limiting RSS, since it doesn't directly reflect real, limited resources (RAM and swap) on the host, that deprive other virtual machines of those resources. Bertl says that AS limits can be used to give guests a "gentle" warning that they are running out of memory, but I don't know how much more gentle it is, or how to set it accurately.

For example, 100 processes each mapping a 100 MB file would consume a total of 10 GB of address space (AS), but no more than 100 MB of resources on the host. But if you set the AS limit to 10 GB, then it will not stop one process from allocating 4 GB of RAM, which could kill the host or result in that process being killed by the OOM killer.

this is posted by siddharth

== Setting memory limits ==
'''Beginning with vs2.3.0.36.29 you should use cgroups to set memory limits. More information: [[util-vserver:Cgroups#using_cgroup_to_enforce_memory_limits|using cgroup to enforce memory limits]]'''

You can set the hard limit on a particular context, effective immediately, with this command:

<pre>
/usr/sbin/vlimit -c <xid> --<resource> <value>
</pre>

<code><xid></code> is the context ID of the guest, which you can determine with the <code>/usr/sbin/vserver-stat</code> command.

For example, if you want to change the '''rss''' hard limit for the vserver with <code><xid></code> 49000, and limit it to 10,000 pages (40 MB), you could use this command:

<pre>
/usr/sbin/vlimit -c 49000 --rss 10000
</pre>

You can change the soft limit instead by adding the <code>-S</code> parameter.

Changes made with the vlimit command are effective only until the vserver is stopped. To make permanent changes, write the value to this file:

<pre>
/etc/vservers/<name>/rlimits/<resource>.hard
</pre>

To set a soft limit, use the same file name with the <code>.soft</code> extension. The <code>rlimits</code> directory is not created by default, so you may need to create it yourself.

If you omit the suffix after the <code>/etc/vservers/<name>/rlimits/rss</code> file, the value will be set for both, the hard and soft limit.

Changes to these files take effect only when the vserver is started. To make immediate and permanent changes to a running vserver, you need to run <code>vlimit</code> '''and''' update the rlimits file.

The safest setting, to prevent any guest from interfering with any other, is to set the total of all RSS hard limits (across all running guests) to be less than the total virtual memory (RAM and swap) on the host. It should be sufficiently less to leave room for processes running on the host, and some disk cache, perhaps 100 MB.

However, this is very conservative, since it assumes the worst case where all guests are using the maximum amount of memory at one time. In practice, you can usually get away with contended resources, i.e. allowing guests to use more than this value.

== Displaying current memory limits ==
To display the currently active RSS limits for a vserver execute the following command:
<pre>
vlimit -c <xid> -a -d | grep RSS
</pre>

The above command will display a similar result, whereas the third value (5000) is the soft limit and the last reflects the current hard limit (10000).
<pre>
RSS N/A 5000 10000
</pre>

== Display memory limits within a vserver ==
Normally the <code>top</code> and <code>free</code> command will display the RAM and Swap usage of the host while invoked within a vserver. To change this behavior, add the <code>VIRT_MEM</code> [[Capabilities_and_Flags#Context_flags_.28cflags.29|context flag]] to your vserver configuration:
<pre>
echo "VIRT_MEM" >> /etc/vservers/<name>/flags
</pre>

After a successful restart of the related vserver, the total available RAM will equal to the value of <code>rss.soft</code> while the difference of <code>rss.hard</code> - <code>rss.soft</code> will be displayed as swap space.

As an example, if you set the <code>rss.hard</code> limit to 10'000 pages and the <code>rss.soft</code> limit to 7'000 pages:
<pre>
vlimit -c <xid> --rss 10000
vlimit -c <xid> -S --rss 7000
vlimit -c <xid> -a -d | grep RSS
</pre>
<pre>
RSS N/A 7000 10000
</pre>

<code>free</code> will report 28'000 KB (7'000 pages) of total memory and 12'000 KB (10'000 - 7'000 pages) of Swap space (assuming that one page is 4 KB):
<pre>
free -k
</pre>
<pre>
total used free shared buffers cached
Mem: 28000 4396 23604 0 0 0
-/+ buffers/cache: 4396 23604
Swap: 12000 0 12000
</pre>

'''Note:''' According to Herbert, the kernel won't use any ''real'' swap as soon as the <code>rss.soft</code> limit has been reached. Swapping will be done on the host level, not per vserver (see [http://list.linux-vserver.org/archive?mss:653:200801:iiagcodpghkhehndkgjg "free" command inside vserver]).

Standard non-shared quota

2009-06-02T11:20:17Z

Skaboom: /* Save settings for reboot */

Want to enable quotas from within a vserver, nothing special, just plain old and good quota support? Then this might help you!
First things first, you will need a vserver enabled kernel that you have made working and you need to add vroot support to it (In menuconfig it is in Device Drivers → Block Devices → Virtual Root device support).

After booting on the vroot enabled vserver kernel, you should have a directory '''/dev/vroot/''' with 8 vroot devices (0-7) you can use to set up your quota, if you don't, then you may make them by mknod /dev/vroot/n b 4 n (where n can be from 0 to 7). If your Linux distribution uses ''udev'', these will be at '''/dev/vroot[0-7]''' instead.

== Initial Setup ==
First, ensure that the filesystem where your vservers are located on the host has quota options enabled: usrquota,grpquota

Edit your /etc/fstab if this is not the case. You don't need to actually enable quotas in the host, but you at least need the usrquota and grpquota mount options.

Then, use ''vrsetup'' to tell the kernel what block device you want to handle quota for:
vrsetup /dev/vroot/0 [partition]
Where [partition] is your /vservers partition. For example, this could be something like /dev/hda5 if you're just using standard partitioning, or something like /dev/lvm/vserver0 if you're using LVM.

== Setting Up Vservers For Quota ==
Setting up the vserver for quota is straight forward: (you need util-vserver 30.208 or newer)

1. Create a default mtab for the guest. To do this, add:
/dev/hdv1 / ufs rw,usrquota,grpquota 0 0
to '''/etc/vservers/<name>/apps/init/mtab'''

Note: Replace <code>ufs</code> with <code>xfs</code> if you're using an XFS file-system.

2. Add the quota capability to the guest vserver. Add:
quota_ctl
to '''/etc/vservers/<name>/ccapabilities'''

3. Copy the vroot device which we setup earlier to the vserver:
cp -af /dev/vroot/0 /vservers/<name>/dev/hdv1

=== Finishing the setup ===
1. Start your guest.<br />
2. Inside the guest, make sure the mtab entry is present:
<pre>
grep /dev/hdv1 /etc/mtab
</pre>
<pre>
/dev/hdv1 / ufs rw,usrquota,grpquota 0 0
</pre>

Afterwards run
quotacheck -maugv

3. Still inside the guest, turn quotas on.

=== Save settings for reboot ===
To have setting persist on reboot, put vrsetup line into '''/etc/init.d/util-vserver''' start function, so after reboot vroot device get setup before it start.

Alternatively add the vrsetup line to the '''/etc/vservers/<vserver-name>/scripts/initialize''' script:
<pre>
echo "/usr/sbin/vrsetup /dev/vroot/0 [partition]" >> /etc/vservers/<vserver-name>/scripts/initialize
</pre>

and the vrsetup detach command into '''/etc/vservers/<vserver-name>/scripts/postpost-stop''':
<pre>
echo "/usr/sbin/vrsetup -d /dev/vroot/0" >> /etc/vservers/<vserver-name>/scripts/postpost-stop
</pre>

Standard non-shared quota

2009-06-01T16:32:55Z

Skaboom: /* Save settings for reboot */

Want to enable quotas from within a vserver, nothing special, just plain old and good quota support? Then this might help you!
First things first, you will need a vserver enabled kernel that you have made working and you need to add vroot support to it (In menuconfig it is in Device Drivers → Block Devices → Virtual Root device support).

After booting on the vroot enabled vserver kernel, you should have a directory '''/dev/vroot/''' with 8 vroot devices (0-7) you can use to set up your quota, if you don't, then you may make them by mknod /dev/vroot/n b 4 n (where n can be from 0 to 7). If your Linux distribution uses ''udev'', these will be at '''/dev/vroot[0-7]''' instead.

== Initial Setup ==
First, ensure that the filesystem where your vservers are located on the host has quota options enabled: usrquota,grpquota

Edit your /etc/fstab if this is not the case. You don't need to actually enable quotas in the host, but you at least need the usrquota and grpquota mount options.

Then, use ''vrsetup'' to tell the kernel what block device you want to handle quota for:
vrsetup /dev/vroot/0 [partition]
Where [partition] is your /vservers partition. For example, this could be something like /dev/hda5 if you're just using standard partitioning, or something like /dev/lvm/vserver0 if you're using LVM.

== Setting Up Vservers For Quota ==
Setting up the vserver for quota is straight forward: (you need util-vserver 30.208 or newer)

1. Create a default mtab for the guest. To do this, add:
/dev/hdv1 / ufs rw,usrquota,grpquota 0 0
to '''/etc/vservers/<name>/apps/init/mtab'''

Note: Replace <code>ufs</code> with <code>xfs</code> if you're using an XFS file-system.

2. Add the quota capability to the guest vserver. Add:
quota_ctl
to '''/etc/vservers/<name>/ccapabilities'''

3. Copy the vroot device which we setup earlier to the vserver:
cp -af /dev/vroot/0 /vservers/<name>/dev/hdv1

=== Finishing the setup ===
1. Start your guest.<br />
2. Inside the guest, make sure the mtab entry is present:
<pre>
grep /dev/hdv1 /etc/mtab
</pre>
<pre>
/dev/hdv1 / ufs rw,usrquota,grpquota 0 0
</pre>

Afterwards run
quotacheck -maugv

3. Still inside the guest, turn quotas on.

=== Save settings for reboot ===
To have setting persist on reboot, put vrsetup line into '''/etc/init.d/util-vserver''' start function, so after reboot vroot device get setup before it start.

Alternatively add the vrsetup line to the '''/etc/vservers/<vserver-name>/scripts/initialize''' script:
<pre>
echo "vrsetup /dev/vroot/0 [partition]" >> /etc/vservers/<vserver-name>/scripts/initialize
</pre>

and the vrsetup detach command into '''/etc/vservers/<vserver-name>/scripts/postpost-stop''':
<pre>
echo "vrsetup -d /dev/vroot/0" >> /etc/vservers/<vserver-name>/scripts/postpost-stop
</pre>

Standard non-shared quota

2009-06-01T15:46:43Z

Skaboom:

Standard non-shared quota

2009-06-01T15:45:55Z

Skaboom: /* Setting Up Vservers For Quota */

Want to enable quotas from within a vserver, nothing special, just plain old and good quota support? Then this might help you!
First things first, you will need a vserver enabled kernel that you have made working and you need to add vroot support to it (In menuconfig it is in Device Drivers → Block Devices → Virtual Root device support).

After booting on the vroot enabled vserver kernel, you should have a directory '''/dev/vroot/''' with 8 vroot devices (0-7) you can use to set up your quota, if you don't, then you may make them by mknod /dev/vroot/n b 4 n (where n can be from 0 to 7). If your Linux distribution uses ''udev'', these will be at '''/dev/vroot[0-7]''' instead.

== Initial Setup ==
First, ensure that the filesystem where your vservers are located on the host has quota options enabled: usrquota,grpquota

Edit your /etc/fstab if this is not the case. You don't need to actually enable quotas in the host, but you at least need the usrquota and grpquota mount options.

Then, use ''vrsetup'' to tell the kernel what block device you want to handle quota for:
vrsetup /dev/vroot/0 [partition]
Where [partition] is your /vservers partition. For example, this could be something like /dev/hda5 if you're just using standard partitioning, or something like /dev/lvm/vserver0 if you're using LVM.

== Setting Up Vservers For Quota ==
Setting up the vserver for quota is straight forward: (you need util-vserver 30.208 or newer)

1. Create a default mtab for the guest. To do this, add:
/dev/hdv1 / ufs rw,usrquota,grpquota 0 0
to '''/etc/vservers/<name>/apps/init/mtab'''

Note: Replace <code>ufs</code> with <code>xfs</code> if you're using an XFS file-system.

2. Add the quota capability to the guest vserver. Add:
quota_ctl
to '''/etc/vservers/<name>/ccapabilities'''

3. Copy the vroot device which we setup earlier to the vserver:
cp -af /dev/vroot/0 /vservers/<name>/dev/hdv1

=== Finishing the setup ===

1. Start your guest.<br />
2. Inside the guest, make sure the mtab entry is present:
<pre>
grep /dev/hdv1 /etc/mtab
</pre>
<pre>
/dev/hdv1 / ufs rw,usrquota,grpquota 0 0
</pre>

Afterwards run
quotacheck -maugv

3. Still inside the guest, turn quotas on.

=== Save settings for reboot ===
To have setting persist on reboot, put vrsetup line into '''/etc/init.d/util-vserver''' start function, so after reboot vroot device get setup before it start.

Memory Limits

2008-03-21T17:39:53Z

Skaboom: /* Display memory limits within a vserver */

== Overview ==
A vserver kernel keeps track many resources used by each guest (context). Some of these relate to memory usage by the guest. You can place limits on these resources to prevent guests from using all the host memory and making the host unusable.

Two resources are particularly important in this regard:

* The '''Resident Set Size''' (<code>rss</code>) is the amount of pages currently present in RAM.
* The '''Address Space''' (<code>as</code>) is the total amount of memory (pages) mapped in each process in the context.

Both are measured in '''pages''', which are 4 kB each on Intel machines (i386). So a value of 200000 means a limit of 800,000 kB, a little less than 800 MB.

Each resource has a '''soft''' and a '''hard limit'''.

* If a guest exceeds the <code>rss</code> hard limit, the kernel will invoke the Out-of-Memory (OOM) killer to kill some process in the guest.
* The <code>rss</code> soft limit is shown inside the guest as the maximum available memory. If a guest exceeds the <code>rss</code> soft limit, it will get an extra "bonus" for the OOM killer (proportional to the oversize).
* If a guest exceeds the <code>as</code> hard limit, memory allocation attempts will return an error, but no process is killed.
* The <code>as</code> soft limit is not in utilized until now. In the future it may be used to penalizing guests over that limit or it could be used to force swapping on them and such ...

Bertl explained the difference between '''rss''' and '''as''' with the following example. If two processes share 100 MB of memory, then only 100 MB worth of virtual memory pages can be used at most, so the RSS use of the guest increases by 100 MB. However, two processes are using it, so the AS use increases by 200 MB.

This makes me think that limiting AS is less useful than limiting RSS, since it doesn't directly reflect real, limited resources (RAM and swap) on the host, that deprive other virtual machines of those resources. Bertl says that AS limits can be used to give guests a "gentle" warning that they are running out of memory, but I don't know how much more gentle it is, or how to set it accurately.

For example, 100 processes each mapping a 100 MB file would consume a total of 10 GB of address space (AS), but no more than 100 MB of resources on the host. But if you set the AS limit to 10 GB, then it will not stop one process from allocating 4 GB of RAM, which could kill the host or result in that process being killed by the OOM killer.

== Setting memory limits ==
You can set the hard limit on a particular context, effective immediately, with this command:

<pre>
/usr/sbin/vlimit -c <xid> --<resource> <value>
</pre>

<code><xid></code> is the context ID of the guest, which you can determine with the <code>/usr/sbin/vserver-stat</code> command.

For example, if you want to change the '''rss''' hard limit for the vserver with <code><xid></code> 49000, and limit it to 10,000 pages (40 MB), you could use this command:

<pre>
/usr/sbin/vlimit -c 49000 --rss 10000
</pre>

You can change the soft limit instead by adding the <code>-S</code> parameter.

Changes made with the vlimit command are effective only until the vserver is stopped. To make permanent changes, write the value to this file:

<pre>
/etc/vservers/<name>/rlimits/<resource>.hard
</pre>

To set a soft limit, use the same file name with the <code>.soft</code> extension. The <code>rlimits</code> directory is not created by default, so you may need to create it yourself.

If you omit the suffix after the <code>/etc/vservers/<name>/rlimits/rss</code> file, the value will be set for both, the hard and soft limit.

Changes to these files take effect only when the vserver is started. To make immediate and permanent changes to a running vserver, you need to run <code>vlimit</code> '''and''' update the rlimits file.

The safest setting, to prevent any guest from interfering with any other, is to set the total of all RSS hard limits (across all running guests) to be less than the total virtual memory (RAM and swap) on the host. It should be sufficiently less to leave room for processes running on the host, and some disk cache, perhaps 100 MB.

However, this is very conservative, since it assumes the worst case where all guests are using the maximum amount of memory at one time. In practice, you can usually get away with contended resources, i.e. allowing guests to use more than this value.

== Displaying current memory limits ==
To display the currently active RSS limits for a vserver execute the following command:
<pre>
vlimit -c <xid> -a -d | grep RSS
</pre>

The above command will display a similar result, whereas the third value (5000) is the soft limit and the last reflects the current hard limit (10000).
<pre>
RSS N/A 5000 10000
</pre>

== Display memory limits within a vserver ==
Normally the <code>top</code> and <code>free</code> command will display the RAM and Swap usage of the host while invoked within a vserver. To change this behavior, add the <code>VIRT_MEM</code> [[Capabilities_and_Flags#Context_flags_.28cflags.29|context flag]] to your vserver configuration:
<pre>
echo "VIRT_MEM" >> /etc/vservers/<name>/flags
</pre>

After a successful restart of the related vserver, the total available RAM will equal to the value of <code>rss.soft</code> while the difference of <code>rss.hard</code> - <code>rss.soft</code> will be displayed as swap space.

As an example, if you set the <code>rss.hard</code> limit to 10'000 pages and the <code>rss.soft</code> limit to 7'000 pages:
<pre>
vlimit -c <xid> --rss 10000
vlimit -c <xid> -S -rss 7000
vlimit -c basesystem-vserver -a -d | grep RSS
</pre>
<pre>
RSS N/A 7000 10000
</pre>

<code>free</code> will report 28'000 KB of total memory and 12'000 KB of Swap space (assuming that one page is 4 KB):
<pre>
free -k
</pre>
<pre>
total used free shared buffers cached
Mem: 28000 4396 23604 0 0 0
-/+ buffers/cache: 4396 23604
Swap: 12000 0 12000
</pre>

'''Note:''' According to Herbert, the kernel won't use any ''real'' swap as soon as the <code>rss.soft</code> limit has been reached. Swapping will be done on the host level, not per vserver (see [http://list.linux-vserver.org/archive?mss:653:200801:iiagcodpghkhehndkgjg "free" command inside vserver]).

Memory Limits

2008-01-27T13:18:58Z

Skaboom:

== Overview ==
A vserver kernel keeps track many resources used by each guest (context). Some of these relate to memory usage by the guest. You can place limits on these resources to prevent guests from using all the host memory and making the host unusable.

Two resources are particularly important in this regard:

* The '''Resident Set Size''' (<code>rss</code>) is the amount of pages currently present in RAM.
* The '''Address Space''' (<code>as</code>) is the total amount of memory (pages) mapped in each process in the context.

Both are measured in '''pages''', which are 4 kB each on Intel machines (i386). So a value of 200000 means a limit of 800,000 kB, a little less than 800 MB.

Each resource has a '''soft''' and a '''hard limit'''.

* If a guest exceeds the <code>rss</code> hard limit, the kernel will invoke the Out-of-Memory (OOM) killer to kill some process in the guest.
* The <code>rss</code> soft limit is shown inside the guest as the maximum available memory. If a guest exceeds the <code>rss</code> soft limit, it will get an extra "bonus" for the OOM killer (proportional to the oversize).
* If a guest exceeds the <code>as</code> hard limit, memory allocation attempts will return an error, but no process is killed.
* The <code>as</code> soft limit is not in utilized until now. In the future it may be used to penalizing guests over that limit or it could be used to force swapping on them and such ...

Bertl explained the difference between '''rss''' and '''as''' with the following example. If two processes share 100 MB of memory, then only 100 MB worth of virtual memory pages can be used at most, so the RSS use of the guest increases by 100 MB. However, two processes are using it, so the AS use increases by 200 MB.

This makes me think that limiting AS is less useful than limiting RSS, since it doesn't directly reflect real, limited resources (RAM and swap) on the host, that deprive other virtual machines of those resources. Bertl says that AS limits can be used to give guests a "gentle" warning that they are running out of memory, but I don't know how much more gentle it is, or how to set it accurately.

For example, 100 processes each mapping a 100 MB file would consume a total of 10 GB of address space (AS), but no more than 100 MB of resources on the host. But if you set the AS limit to 10 GB, then it will not stop one process from allocating 4 GB of RAM, which could kill the host or result in that process being killed by the OOM killer.

== Setting memory limits ==
You can set the hard limit on a particular context, effective immediately, with this command:

<pre>
/usr/sbin/vlimit -c <xid> --<resource> <value>
</pre>

<code><xid></code> is the context ID of the guest, which you can determine with the <code>/usr/sbin/vserver-stat</code> command.

For example, if you want to change the '''rss''' hard limit for the vserver with <code><xid></code> 49000, and limit it to 10,000 pages (40 MB), you could use this command:

<pre>
/usr/sbin/vlimit -c 49000 --rss 10000
</pre>

You can change the soft limit instead by adding the <code>-S</code> parameter.

Changes made with the vlimit command are effective only until the vserver is stopped. To make permanent changes, write the value to this file:

<pre>
/etc/vservers/<name>/rlimits/<resource>.hard
</pre>

To set a soft limit, use the same file name with the <code>.soft</code> extension. The <code>rlimits</code> directory is not created by default, so you may need to create it yourself.

If you omit the suffix after the <code>/etc/vservers/<name>/rlimits/rss</code> file, the value will be set for both, the hard and soft limit.

Changes to these files take effect only when the vserver is started. To make immediate and permanent changes to a running vserver, you need to run <code>vlimit</code> '''and''' update the rlimits file.

The safest setting, to prevent any guest from interfering with any other, is to set the total of all RSS hard limits (across all running guests) to be less than the total virtual memory (RAM and swap) on the host. It should be sufficiently less to leave room for processes running on the host, and some disk cache, perhaps 100 MB.

However, this is very conservative, since it assumes the worst case where all guests are using the maximum amount of memory at one time. In practice, you can usually get away with contended resources, i.e. allowing guests to use more than this value.

== Displaying current memory limits ==
To display the currently active RSS limits for a vserver execute the following command:
<pre>
vlimit -c <xid> -a -d | grep RSS
</pre>

The above command will display a similar result, whereas the third value (5000) is the soft limit and the last reflects the current hard limit (10000).
<pre>
RSS N/A 5000 10000
</pre>

== Display memory limits within a vserver ==
Normally the <code>top</code> and <code>free</code> command will display the RAM and Swap usage of the host while invoked within a vserver. To change this behavior, add the <code>VIRT_MEM</code> [[Capabilities_and_Flags#Context_flags_.28cflags.29|context flag]] to your vserver configuration:
<pre>
echo "VIRT_MEM" >> /etc/vservers/<name>/flags
</pre>

After a successful restart of the related vserver, the total available RAM will show as the difference of <code>rss.hard</code> - <code>rss.soft</code> while the remainder will be displayed as swap space.

'''Note:''' According to Herbert, the kernel won't use any ''real'' swap as soon as the <code>rss.soft</code> limit has been reached. Swapping will be done on the host level, not per vserver (see [http://list.linux-vserver.org/archive?mss:653:200801:iiagcodpghkhehndkgjg "free" command inside vserver]).