Soft Patch Panel
 help / color / mirror / Atom feed
Subject: [spp] [PATCH 5/5] docs: add note regarding NUMA configuration
Date: Fri, 05 Jun 2020 09:28:54 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

From: Hideyuki Yamashita <>

This patch adds new notes for NUMA configuration when starting

This is pointed out by the following DPDK Bugzilla tickets.

Signed-off-by: Hideyuki Yamashita <>
Signed-off-by: Naoki Takada <>
 docs/guides/gsg/howto_use.rst | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/guides/gsg/howto_use.rst b/docs/guides/gsg/howto_use.rst
index f182198..4f2e6cd 100644
--- a/docs/guides/gsg/howto_use.rst
+++ b/docs/guides/gsg/howto_use.rst
@@ -422,6 +422,18 @@ if you run the process on single NUMA node.
    If you use DPDK v18.11 or later, ``--base-virtaddr 0x100000000`` is enabled
    in default. You need to use this option only for changing the default value.
+.. note::
+   ``spp_primary`` tries to create memory pool in the same NUMA node where
+   it is launched. Under NUMA configuration, the NUMA node where ``spp_primary``
+   is launched and the NUMA node where NIC is connected can be different
+   (e.g. spp_primary runs in NUMA node 0 while NIC is connected with NUMA
+   node 1).
+   Such configuration may cause performance degradation. In general, under
+   NUMA configuration, it is best practice to use CPU and NIC which belongs
+   to the same NUMA node for best performance. So user should align those
+   when performance degradation makes the situation critical.
 If ``spp_primary`` is launched with two or more lcores, forwarder or monitor
 is activated. The default is forwarder and monitor is optional in this case.
 If you use monitor thread, additional option ``--disp-stat`` is required.

  parent reply	other threads:[~2020-06-05  0:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05  0:28 [spp] [PATCH 0/5] updates for catching up DPDK20.02 x-fn-spp-ml
2020-06-05  0:28 ` [spp] [PATCH 1/5] docs: remove unnecessary usage of ethtool x-fn-spp-ml
2020-06-05  0:28 ` [spp] [PATCH 2/5] docs: resolve broken reference link x-fn-spp-ml
2020-06-05  0:28 ` [spp] [PATCH 3/5] docs: catch up updates in dpdk-20.02 x-fn-spp-ml
2020-06-08  8:02   ` Yasufumi Ogawa
2020-06-16  8:28     ` [spp] (x-fn-spp-ml 781) " Hideyuki Yamashita
2020-06-05  0:28 ` [spp] [PATCH 4/5] makefile: change default build target x-fn-spp-ml
2020-06-05  0:28 ` x-fn-spp-ml [this message]
2020-06-08  8:21   ` [spp] [PATCH 5/5] docs: add note regarding NUMA configuration Yasufumi Ogawa
2020-06-16  8:30     ` [spp] (x-fn-spp-ml 783) " Hideyuki Yamashita
2020-06-16 16:18       ` Yasufumi Ogawa
2020-06-18  3:14         ` [spp] (x-fn-spp-ml 796) " Hideyuki Yamashita
2020-06-05  2:40 ` [spp] [PATCH 0/5] updates for catching up DPDK20.02 Itsuro ODA

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).