From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 0521A106A for ; Fri, 9 Dec 2016 16:14:55 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga102.jf.intel.com with ESMTP; 09 Dec 2016 07:14:54 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,324,1477983600"; d="scan'208";a="200862327" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.64]) by fmsmga004.fm.intel.com with SMTP; 09 Dec 2016 07:14:52 -0800 Received: by (sSMTP sendmail emulation); Fri, 09 Dec 2016 15:14:52 +0000 Date: Fri, 9 Dec 2016 15:14:52 +0000 From: Bruce Richardson To: Thomas Monjalon Cc: Jianfeng Tan , dev@dpdk.org, david.marchand@6wind.com, pmatilai@redhat.com Message-ID: <20161209151451.GB14536@bricha3-MOBL3.ger.corp.intel.com> References: <1472693507-11369-1-git-send-email-jianfeng.tan@intel.com> <1480700936-8450-1-git-send-email-jianfeng.tan@intel.com> <1697449.uzq8KWsvfF@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1697449.uzq8KWsvfF@xps13> Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.7.1 (2016-10-04) Subject: Re: [dpdk-dev] [PATCH v4] eal: restrict cores auto detection 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: Fri, 09 Dec 2016 15:14:57 -0000 On Thu, Dec 08, 2016 at 07:19:41PM +0100, Thomas Monjalon wrote: > 2016-12-02 17:48, Jianfeng Tan: > > This patch uses pthread_getaffinity_np() to narrow down used > > cores when none of below options is specified: > > * coremask (-c) > > * corelist (-l) > > * and coremap (--lcores) > > > > The purpose of this patch is to leave out these core related options > > when DPDK applications are deployed under container env, so that > > users do not need decide the core related parameters when developing > > applications. Instead, when applications are deployed in containers, > > use cpu-set to constrain which cores can be used inside this container > > instance. And DPDK application inside containers just rely on this > > auto detect mechanism to start polling threads. > > > > Note: previously, some users are using isolated CPUs, which could > > be excluded by default. Please add commands like taskset to use > > those cores. > > > > Test example: > > $ taskset 0xc0000 ./examples/helloworld/build/helloworld -m 1024 > > Bruce, what do you think of this version? > It requires taskset only if -c, -l and --lcores are not used. > I'm fine with that since it maintains backward compatibilty for those options. Acked-by: Bruce Richardson