Fix duplicate include issue
Removed duplicate note at top if allocating-host-memory-using-horizon.rst Removed start and end include markers that contains only one text chunk Made path to include relative to root in allocating-host-memory-using-the-cli.rst Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ibf1d80e7a6cffc3cf3d01fc0c5773426822d2ce2
This commit is contained in:
parent
0a0854caa3
commit
e41b3724c4
@ -1,5 +0,0 @@
|
|||||||
.. introduction-text-begin
|
|
||||||
.. introduction-text-end
|
|
||||||
|
|
||||||
.. usage-text-begin
|
|
||||||
.. usage-text-end
|
|
@ -15,8 +15,6 @@ Allocate Host Memory Using Horizon
|
|||||||
.. only:: partner
|
.. only:: partner
|
||||||
|
|
||||||
.. include:: /_includes/avs-note.rest
|
.. include:: /_includes/avs-note.rest
|
||||||
:start-after: introduction-text-begin
|
|
||||||
:end-before: introduction-text-end
|
|
||||||
|
|
||||||
Due to limitations in Kubernetes, only a single huge page size can be used
|
Due to limitations in Kubernetes, only a single huge page size can be used
|
||||||
per host.
|
per host.
|
||||||
@ -25,12 +23,6 @@ per host.
|
|||||||
|
|
||||||
A node may only allocate huge pages for a single size, either 2MiB or 1GiB.
|
A node may only allocate huge pages for a single size, either 2MiB or 1GiB.
|
||||||
|
|
||||||
.. only:: partner
|
|
||||||
|
|
||||||
.. include:: /_includes/avs-note.rest
|
|
||||||
:start-after: usage-text-begin
|
|
||||||
:end-before: usage-text-end
|
|
||||||
|
|
||||||
You must also provision one 1GiB huge page per |NUMA| node prior to unlocking a
|
You must also provision one 1GiB huge page per |NUMA| node prior to unlocking a
|
||||||
worker or an |AIO| controller.
|
worker or an |AIO| controller.
|
||||||
|
|
||||||
|
@ -231,4 +231,4 @@ worker or an |AIO| controller.
|
|||||||
|
|
||||||
.. only:: partner
|
.. only:: partner
|
||||||
|
|
||||||
.. include:: ../../../_includes/avs-note.rest
|
.. include:: /_includes/avs-note.rest
|
||||||
|
Loading…
x
Reference in New Issue
Block a user