From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1C8B2A00C4 for ; Fri, 5 Jun 2020 02:29:04 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9AE491D61B; Fri, 5 Jun 2020 02:29:03 +0200 (CEST) Received: from dish-sg.nttdocomo.co.jp (dish-sg.nttdocomo.co.jp [202.19.227.74]) by dpdk.org (Postfix) with ESMTP id 8ECC71D61B for ; Fri, 5 Jun 2020 02:29:02 +0200 (CEST) X-dD-Source: Outbound Received: from zssg-mailmd105.ddreams.local (zssg-mailmd900.ddreams.local [10.160.172.63]) by zssg-mailou102.ddreams.local (Postfix) with ESMTP id 8F1CB1200F5; Fri, 5 Jun 2020 09:29:01 +0900 (JST) Received: from zssg-mailmf105.ddreams.local (zssg-mailmf900.ddreams.local [10.160.172.84]) by zssg-mailmd105.ddreams.local (dDREAMS) with ESMTP id <0QBF010E3G0DJ930@dDREAMS>; Fri, 05 Jun 2020 09:29:01 +0900 (JST) Received: from zssg-mailmf105.ddreams.local (unknown [127.0.0.1]) by zssg-mailmf105.ddreams.local (Postfix) with ESMTP id 6FE1B7E603A; Fri, 5 Jun 2020 09:29:01 +0900 (JST) Received: from zssg-mailmf105.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 6DF3E8E6060; Fri, 5 Jun 2020 09:29:01 +0900 (JST) Received: from localhost (unknown [127.0.0.1]) by IMSVA (Postfix) with SMTP id 6BFA08E605D; Fri, 5 Jun 2020 09:29:01 +0900 (JST) X-IMSS-HAND-OFF-DIRECTIVE: localhost:10026 Received: from zssg-mailmf105.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 269478E6058; Fri, 5 Jun 2020 09:29:00 +0900 (JST) Received: from davinci.ntt-tx.co.jp (unknown [10.160.183.139]) by zssg-mailmf105.ddreams.local (Postfix) with ESMTP; Fri, 5 Jun 2020 09:29:00 +0900 (JST) From: x-fn-spp-ml@ntt-tx.co.jp To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com Date: Fri, 05 Jun 2020 09:28:54 +0900 Message-id: <20200605002854.24054-6-x-fn-spp-ml@ntt-tx.co.jp> X-Mailer: git-send-email 2.25.1 In-reply-to: <20200605002854.24054-1-x-fn-spp-ml@ntt-tx.co.jp> References: <20200605002854.24054-1-x-fn-spp-ml@ntt-tx.co.jp> MIME-version: 1.0 Content-transfer-encoding: 8bit X-TM-AS-GCONF: 00 Subject: [spp] [PATCH 5/5] docs: add note regarding NUMA configuration X-BeenThere: spp@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Soft Patch Panel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: spp-bounces@dpdk.org Sender: "spp" From: Hideyuki Yamashita This patch adds new notes for NUMA configuration when starting spp_primary. This is pointed out by the following DPDK Bugzilla tickets. https://bugs.dpdk.org/show_bug.cgi?id=457 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. -- 2.25.1