From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id A73561E34 for ; Sat, 6 May 2017 02:52:21 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 May 2017 17:52:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,295,1491289200"; d="scan'208";a="1144307357" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga001.fm.intel.com with ESMTP; 05 May 2017 17:52:19 -0700 Received: from fmsmsx157.amr.corp.intel.com (10.18.116.73) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 5 May 2017 17:52:19 -0700 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by FMSMSX157.amr.corp.intel.com (10.18.116.73) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 5 May 2017 17:52:18 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.117]) by SHSMSX104.ccr.corp.intel.com ([10.239.4.70]) with mapi id 14.03.0319.002; Sat, 6 May 2017 08:52:17 +0800 From: "Wu, Jingjing" To: "Pei, Yulong" , "dev@dpdk.org" CC: "thomas@monjalon.net" Thread-Topic: [PATCH v5] app/testpmd: fix port_numa and ring_numa not initialize issue Thread-Index: AQHSxLoRTxn1/pZTYUef+U1ottjed6HmfHhQ Date: Sat, 6 May 2017 00:52:16 +0000 Message-ID: <9BB6961774997848B5B42BEC655768F810D623C3@SHSMSX103.ccr.corp.intel.com> References: <1493344915-127542-1-git-send-email-yulong.pei@intel.com> <1493807387-135918-1-git-send-email-yulong.pei@intel.com> In-Reply-To: <1493807387-135918-1-git-send-email-yulong.pei@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v5] app/testpmd: fix port_numa and ring_numa not initialize issue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 May 2017 00:52:22 -0000 > -----Original Message----- > From: Pei, Yulong > Sent: Wednesday, May 3, 2017 6:30 PM > To: dev@dpdk.org > Cc: Wu, Jingjing ; thomas@monjalon.net > Subject: [PATCH v5] app/testpmd: fix port_numa and ring_numa not initiali= ze > issue >=20 > Previous numa_support =3D 0 by default, it need to add --numa to testpmd > command line to enable numa, so port_numa and ring_numa were initialized = at > function launch_args_parse(), now testpmd change numa_support =3D 1 as de= fault, > so port_numa and ring_numa also need to initialize by default, otherwise = port- > >socket_id will be probed to wrong value. >=20 > Fixes: 999b2ee0fe45 ("app/testpmd: enable NUMA support by default") >=20 > Signed-off-by: Yulong Pei Acked-by: Jingjing Wu