From: <pbhagavatula@marvell.com>
Cc: <stephen@networkplumber.org>, <jerinj@marvell.com>,
<dev@dpdk.org>, "Pavan Nikhilesh" <pbhagavatula@marvell.com>
Subject: [PATCH v2] doc: update Linux core isolation guide
Date: Tue, 17 May 2022 23:38:55 +0530 [thread overview]
Message-ID: <20220517180856.1139-1-pbhagavatula@marvell.com> (raw)
In-Reply-To: <20220502072414.4643-1-pbhagavatula@marvell.com>
From: Pavan Nikhilesh <pbhagavatula@marvell.com>
Update Linux core isolation guide to include isolation from
timers, rcu processing and IRQs.
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
v2 Changes:
- Add references to the parameters used.
- Add note about Linux cgroups.
doc/guides/linux_gsg/enable_func.rst | 22 +++++++++++++++++-----
1 file changed, 17 insertions(+), 5 deletions(-)
diff --git a/doc/guides/linux_gsg/enable_func.rst b/doc/guides/linux_gsg/enable_func.rst
index 1df3ab0255..d6f3961da7 100644
--- a/doc/guides/linux_gsg/enable_func.rst
+++ b/doc/guides/linux_gsg/enable_func.rst
@@ -90,16 +90,28 @@ Using Linux Core Isolation to Reduce Context Switches
-----------------------------------------------------
While the threads used by a DPDK application are pinned to logical cores on the system,
-it is possible for the Linux scheduler to run other tasks on those cores also.
-To help prevent additional workloads from running on those cores,
-it is possible to use the ``isolcpus`` Linux kernel parameter to isolate them from the general Linux scheduler.
+it is possible for the Linux scheduler to run other tasks on those cores.
+To help prevent additional workloads, timers, rcu processing and IRQs from running on those cores, it is possible to use
+the Linux kernel parameters ``isolcpus``, ``nohz_full``, ``irqaffinity`` to isolate them from the general Linux scheduler tasks.
-For example, if DPDK applications are to run on logical cores 2, 4 and 6,
+For example, if a given CPU has 0-7 cores and DPDK applications are to run on logical cores 2, 4 and 6,
the following should be added to the kernel parameter list:
.. code-block:: console
- isolcpus=2,4,6
+ isolcpus=2,4,6 nohz_full=2,4,6 irqaffinity=0,1,3,5,7
+
+.. Note::
+
+ More detailed information about the above parameters can be found at
+ https://www.kernel.org/doc/html/latest/timers/no_hz.html
+ https://www.kernel.org/doc/html/latest/core-api/irq/
+ https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html
+
+.. Note::
+
+ For more fine grained control over resource management and performance tuning one can look
+ into ``Linux cgroups``.
.. _High_Precision_Event_Timer:
--
2.25.1
next prev parent reply other threads:[~2022-05-17 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 7:24 [PATCH] " Pavan Nikhilesh
2022-05-02 20:17 ` Stephen Hemminger
2022-05-10 15:50 ` [EXT] " Pavan Nikhilesh Bhagavatula
2022-05-17 18:08 ` pbhagavatula [this message]
2022-05-17 18:22 ` [PATCH v2] " Stephen Hemminger
2022-05-17 18:32 ` [EXT] " Pavan Nikhilesh Bhagavatula
2022-05-17 19:59 ` [PATCH v3] " pbhagavatula
2022-06-02 7:47 ` Jerin Jacob
2022-07-11 20:59 ` Thomas Monjalon
2022-10-31 11:57 ` [PATCH v4] " pbhagavatula
2022-11-15 15:57 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220517180856.1139-1-pbhagavatula@marvell.com \
--to=pbhagavatula@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).