External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-07-30 21:47:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: CPU allocation and pinning clarification

Browse Source 
There was a request for clarifying this part of the
documentation. This also fixes a case used with CPU.
This commit is contained in:
Martin Kletzander 2012-08-27 16:26:26 +02:00
parent 0b4b53bb80
commit 3de747c9a2
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/formatdomain.html.in
View File

@ -369,7 +369,8 @@
if it's specified. If both <code>cpuset</code> and <code>placement</code>
are not specified, or if <code>placement</code> is "static", but no
<code>cpuset</code> is specified, the domain process will be pinned to
all the available physical CPUs.
all the available physical CPUs. These settings are superseded
by <a href="#elementsCPUTuning">CPU tuning</a>.
</dd>
</dl>
@ -404,9 +405,11 @@
</dd>
<dt><code>vcpupin</code></dt>
<dd>
The optional <code>vcpupin</code> element specifies which of host
physical CPUS the domain VCPU will be pinned to. If this is omitted,
each VCPU is pinned to all the physical CPUS by default. It contains two
The optional <code>vcpupin</code> element specifies which of host's
physical CPUs the domain VCPU will be pinned to. This setting supersedes
previous VCPU placement specified in <a href="#elementsCPUAllocation">CPU
Allocation</a> using <code>vcpu</code> element. If this is omitted,
each VCPU is pinned to all the physical CPUs by default. It contains two
required attributes, the attribute <code>vcpu</code> specifies vcpu id,
and the attribute <code>cpuset</code> is same as
attribute <code>cpuset</code>