From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 224218E7E for ; Fri, 15 Jan 2016 11:42:51 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP; 15 Jan 2016 02:42:52 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,299,1449561600"; d="scan'208";a="881934956" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.208.64]) by fmsmga001.fm.intel.com with SMTP; 15 Jan 2016 02:42:50 -0800 Received: by (sSMTP sendmail emulation); Fri, 15 Jan 2016 10:42:48 +0025 Date: Fri, 15 Jan 2016 10:42:48 +0000 From: Bruce Richardson To: Stephen Hurd Message-ID: <20160115104248.GA15840@bricha3-MOBL3> References: <24888901-A45C-4E23-871E-3485AF2423D2@intel.com> <1452723816-73141-1-git-send-email-shurd@broadcom.com> <20160114134418.GA18000@bricha3-MOBL3> <156984479488CD49A184F5CAB4AF9346071A3A00@IRVEXCHMB14.corp.ad.broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <156984479488CD49A184F5CAB4AF9346071A3A00@IRVEXCHMB14.corp.ad.broadcom.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) 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 10:42:52 -0000 On Fri, Jan 15, 2016 at 01:01:04AM +0000, Stephen Hurd wrote: > Found it... > http://www.dpdk.org/ml/archives/dev/2015-December/030564.html > > > -- Stephen Hurd > Thanks for that. For some reason I missed the rest of the email thread from earlier. /Bruce > > -----Original Message----- > From: Bruce Richardson [mailto:bruce.richardson@intel.com] > 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. > > > > Can you clarify why this changes is necessary? Is it causing a bug somewhere? > > thanks, > /Bruce > >