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 3B0E9A04A3 for ; Tue, 16 Jun 2020 10:31:41 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 14F6E1BEA5; Tue, 16 Jun 2020 10:31:41 +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 3B1621BEA5 for ; Tue, 16 Jun 2020 10:31:35 +0200 (CEST) X-dD-Source: Outbound Received: from zssg-mailmd106.ddreams.local (zssg-mailmd900.ddreams.local [10.160.172.63]) by zssg-mailou101.ddreams.local (Postfix) with ESMTP id A2BCC1200FD; Tue, 16 Jun 2020 17:31:30 +0900 (JST) Received: from t131sg-mailcc12.ddreams.local (t131sg-mailcc12.ddreams.local [100.66.31.87]) by zssg-mailmd106.ddreams.local (dDREAMS) with ESMTP id <0QC000OVQFOIQY90@dDREAMS>; Tue, 16 Jun 2020 17:31:30 +0900 (JST) Received: from t131sg-mailcc11 (localhost [127.0.0.1]) by t131sg-mailcc12.ddreams.local (unknown) with SMTP id 05G8VUs9030087; Tue, 16 Jun 2020 17:31:30 +0900 Received: from zssg-mailmf106.ddreams.local (unknown [127.0.0.1]) by zssg-mailmf106.ddreams.local (Postfix) with ESMTP id 8BAB87E603D; Tue, 16 Jun 2020 17:30:14 +0900 (JST) Received: from zssg-mailmf106.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 89D7A8E6066; Tue, 16 Jun 2020 17:30:14 +0900 (JST) Received: from localhost (unknown [127.0.0.1]) by IMSVA (Postfix) with SMTP id 8813B8E605A; Tue, 16 Jun 2020 17:30:14 +0900 (JST) X-IMSS-HAND-OFF-DIRECTIVE: localhost:10026 Received: from zssg-mailmf106.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5A5498E6042; Tue, 16 Jun 2020 17:30:13 +0900 (JST) Received: from zssg-mailua101.ddreams.local (unknown [10.160.172.62]) by zssg-mailmf106.ddreams.local (Postfix) with ESMTP; Tue, 16 Jun 2020 17:30:13 +0900 (JST) Received: from [10.87.198.18] (unknown [10.160.183.129]) by zssg-mailua101.ddreams.local (dDREAMS) with ESMTPA id <0QC000C81FM6WC10@dDREAMS>; Tue, 16 Jun 2020 17:30:06 +0900 (JST) Date: Tue, 16 Jun 2020 17:30:06 +0900 From: Hideyuki Yamashita In-reply-to: References: <20200605002854.24054-6-x-fn-spp-ml@ntt-tx.co.jp> Message-id: <20200616173006.B8F5.17218CA3@ntt-tx.co.jp_1> MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: Becky! ver. 2.74.02 [ja] X-TM-AS-GCONF: 00 To: Yasufumi Ogawa Cc: x-fn-spp-ml@ntt-tx.co.jp, spp@dpdk.org Subject: Re: [spp] (x-fn-spp-ml 783) Re: [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" Hi. Sorry for delayed response. Please see my comments inline. > > 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. > > + > I have two comments. > > 1. Could I confirm WHAT should be configured for avoiding such a performance loss? NUMA node - primary process will run (that can be specified with -l parameter) - NIC belongs should be the same to avoid performance loss. In general, topology regarding with NUMA node (e.g. CPU core, NIC which is connected with specific NUMA node) can be found in lstopo command. > 2. It seems something abruptly considering context of this section because you start talking about performance suddenly. > If it must be considered as a mandatory configuration and should be explained this section, I agree your update. > On the other hand, what do you think to move this note to the next "Performance Optimization" section. > I think no need to be a note if you move it to the next secion. I agree with your idea. I think it is NOT mandatory, thus should be moved to next section 'without' note. > > Thanks > > > 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.