From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1A547A0C43; Mon, 18 Oct 2021 19:53:51 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A230240142; Mon, 18 Oct 2021 19:53:50 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by mails.dpdk.org (Postfix) with ESMTP id D829840141 for ; Mon, 18 Oct 2021 19:53:48 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10141"; a="314522656" X-IronPort-AV: E=Sophos;i="5.85,382,1624345200"; d="scan'208";a="314522656" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Oct 2021 10:53:18 -0700 X-IronPort-AV: E=Sophos;i="5.85,382,1624345200"; d="scan'208";a="443518755" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.28.45]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 18 Oct 2021 10:53:16 -0700 Date: Mon, 18 Oct 2021 18:53:11 +0100 From: Bruce Richardson To: David Marchand Cc: dev@dpdk.org, aconole@redhat.com, blo@iol.unh.edu Message-ID: References: <20211018170136.5189-1-david.marchand@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211018170136.5189-1-david.marchand@redhat.com> Subject: Re: [dpdk-dev] [PATCH] test: rely on EAL detection for core list X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, Oct 18, 2021 at 07:01:36PM +0200, David Marchand wrote: > Cores count has a direct impact on the time needed to complete unit > tests. > > Currently, the core list used for unit test is enforced to "all cores on > the system" with no way for (CI) users to adapt it. > On the other hand, EAL default behavior (when no -c/-l option gets passed) > is to start threads on as many cores available in the process cpu > affinity. > > Remove logic from meson: users can then select where to run the tests by > either running meson with a custom cpu affinity (using taskset/cpuset > depending on OS) or by passing a --test-args option to meson. > > Example: > $ sudo meson test -C build --suite fast-tests -t 3 --test-args "-l 0-3" > > Signed-off-by: David Marchand > --- > I wanted to post this as a RFC, but now, I wonder if all CI test RFC > patches, so sending as a normal patch. > > --- I really like this idea! Patch looks good other than it needs some doc changes.