From: Peter Krempa Date: Fri, 13 May 2022 08:31:32 +0000 (+0200) Subject: docs: formatdomain: Remove 'elementsMemoryTuning' anchor X-Git-Tag: v8.5.0-rc1~275 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=88b97d9bcec29dbbe7b2cfe8d7283511878a9342;p=thirdparty%2Flibvirt.git docs: formatdomain: Remove 'elementsMemoryTuning' anchor Signed-off-by: Peter Krempa Reviewed-by: Ján Tomko --- diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst index fbebff8650..5cf31d9e06 100644 --- a/docs/formatdomain.rst +++ b/docs/formatdomain.rst @@ -1025,7 +1025,7 @@ influence how virtual memory pages are backed by host pages. amounts of locked memory could cause a denial-of-service attack on the host. Because of this, using this option is discouraged unless your workload demands it; even then, it's highly recommended to set a ``hard_limit`` (see - `memory tuning <#elementsMemoryTuning>`__) on memory allocation suitable for + `Memory Tuning`_) on memory allocation suitable for the specific environment at the same time to mitigate the risks described above. :since:`Since 1.0.6` ``source`` @@ -1046,7 +1046,6 @@ influence how virtual memory pages are backed by host pages. this is just an optimization and is not guaranteed to work in all cases (e.g. when hypervisor crashes). :since:`Since 4.4.0` (QEMU/KVM only) -:anchor:`` Memory Tuning -------------