Updated Examples for Application-isolated cores (r5, r6, dsr6, r7, dsr7, r8, dsr8)

Closes Bug: 2007586

Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Change-Id: Id0728682dafe03e362fccfade4092752f9613f98
This commit is contained in:
Juanita-Balaraj
2023-02-16 14:49:53 -05:00
parent 3eacb292c5
commit 010575bf19

View File

@@ -2,9 +2,9 @@
.. bew1572888575258
.. _isolating-cpu-cores-to-enhance-application-performance:
========================================================
Isolate the CPU Cores to Enhance Application Performance
========================================================
====================================================
Isolate CPU Cores to Enhance Application Performance
====================================================
|prod| supports running the most critical low-latency applications on host CPUs
which are completely isolated from the host process scheduler.
@@ -26,6 +26,17 @@ For example:
~(keystone_admin)]$ system host-cpu-modify -f application-isolated -p1 15 worker-1
~(keystone_admin)]$ system host-unlock worker-1
.. note::
It is possible to explicitly specify 1 or more cores or a range of cores to
be application-isolated:
.. code-block::
~(keystone_admin)]$ system host-cpu-modify -f application-isolated -c 3 controller-0
~(keystone_admin)]$ system host-cpu-modify -f application-isolated -c 3,4 controller-0
~(keystone_admin)]$ system host-cpu-modify -f application-isolated -c 3-5 controller-0
All |SMT| siblings (hyperthreads, if enabled) on a core will have the same
assigned function. On host boot, any CPUs designated as isolated will be
specified as part of the isolcpus kernel boot argument, which will isolate them