From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-gw1-out.broadcom.com (mail-gw1-out.broadcom.com [216.31.210.62]) by dpdk.org (Postfix) with ESMTP id 1EC9D8E74 for ; Fri, 15 Jan 2016 02:01:05 +0100 (CET) X-IronPort-AV: E=Sophos;i="5.22,297,1449561600"; d="scan'208";a="85662735" Received: from irvexchmb05.broadcom.com (HELO irvexchmb05.corp.ad.broadcom.com) ([10.9.208.27]) by mail-gw1-out.broadcom.com with ESMTP; 14 Jan 2016 19:40:52 -0800 Received: from IRVEXCHMB14.corp.ad.broadcom.com ([fe80::6184:5cb6:5350:4823]) by irvexchmb05.corp.ad.broadcom.com ([::1]) with mapi id 14.03.0235.001; Thu, 14 Jan 2016 17:01:04 -0800 From: Stephen Hurd To: Bruce Richardson Thread-Topic: [dpdk-dev] [PATCH v2] app/testpmd Fix max_socket detection Thread-Index: AQHRTlEb3ozNst7rzUSga7vKKW4E9p77jM+AgAA27YA= Date: Fri, 15 Jan 2016 01:01:04 +0000 Message-ID: <156984479488CD49A184F5CAB4AF9346071A3A00@IRVEXCHMB14.corp.ad.broadcom.com> References: <24888901-A45C-4E23-871E-3485AF2423D2@intel.com> <1452723816-73141-1-git-send-email-shurd@broadcom.com> <20160114134418.GA18000@bricha3-MOBL3> In-Reply-To: <20160114134418.GA18000@bricha3-MOBL3> Accept-Language: en-CA, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.9.208.64] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd Fix max_socket detection X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2016 01:01:06 -0000 Found it... http://www.dpdk.org/ml/archives/dev/2015-December/030564.html -- Stephen Hurd -----Original Message----- From: Bruce Richardson [mailto:bruce.richardson@intel.com]=20 Sent: Thursday, January 14, 2016 5:44 AM To: Stephen Hurd Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd Fix max_socket detection On Wed, Jan 13, 2016 at 02:23:36PM -0800, Stephen Hurd wrote: > Previously, max_socket was set to the highest numbered socket with > an enabled lcore. The intent is to set it to the highest socket > regardless of it being enabled. >=20 Can you clarify why this changes is necessary? Is it causing a bug somewher= e? thanks, /Bruce