External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 05:35:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Document memory bandwidth allocation limits more clearly

Browse Source 
The meaning of the values as well as their maximums are hard to predict
and accounting for all the possibilities (which by the way might change
during daemon's execution) is borderline hallucinatory.  There is
already a way we represent them, which is the same as the Linux kernel.
We do not interpret them at all, just blindly use them.  In order to
make this more apparent for the users change the documentation for the
<memorytune/> (not <memtune/>) element more boldly.

Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Martin Kletzander 2024-09-10 15:51:59 +02:00
parent eae19bb505
commit b4f93ae8af
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/formatdomain.rst
View File

@ -1018,8 +1018,11 @@ CPU Tuning
``id``
Host node id from which to allocate memory bandwidth.
``bandwidth``
The memory bandwidth to allocate from this node. The value by default
is in percentage.
The memory bandwidth to allocate from this node. The value is usually
in percent (Intel) but can also be in MB/s (if resctrl is mounted with
the ``mba_MBps`` option) or in 1/8 GB/s increments (AMD). The user is
responsible for making sure the value makes sense on their system and
configuration.
Memory Allocation