From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id D47CFA09F0; Thu, 17 Dec 2020 00:29:06 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BD6C0C9DC; Thu, 17 Dec 2020 00:29:04 +0100 (CET) Received: from smtp-fw-2101.amazon.com (smtp-fw-2101.amazon.com [72.21.196.25]) by dpdk.org (Postfix) with ESMTP id 9D0FDC9D0 for ; Thu, 17 Dec 2020 00:29:03 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1608161343; x=1639697343; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=4Y83iAlRw9ocIg7vf+KAb0rPQO1/cpxu2NkxNo56Sz0=; b=DcMm+iWzOA9GIO5oE/SThvLR+sXT8ocnVEdL1eqLccZdiVyENbNrbCXj p5MUfZexlS9fj80SdIs7+IbyzWvIFCvg3z09GKygWkLK3ncwGcwWuQP0x 4u6UKV9AEiQd1uNCNrRvJIREhimcabo0EyH6KgP4a+MP/9Iqgw56y++/c E=; X-IronPort-AV: E=Sophos;i="5.78,425,1599523200"; d="scan'208";a="69607650" Received: from iad12-co-svc-p1-lb1-vlan3.amazon.com (HELO email-inbound-relay-2c-cc689b93.us-west-2.amazon.com) ([10.43.8.6]) by smtp-border-fw-out-2101.iad2.amazon.com with ESMTP; 16 Dec 2020 23:29:00 +0000 Received: from EX13MTAUWB001.ant.amazon.com (pdx1-ws-svc-p6-lb9-vlan3.pdx.amazon.com [10.236.137.198]) by email-inbound-relay-2c-cc689b93.us-west-2.amazon.com (Postfix) with ESMTPS id 1055C120EA3; Wed, 16 Dec 2020 23:29:00 +0000 (UTC) Received: from EX13D02UWB003.ant.amazon.com (10.43.161.48) by EX13MTAUWB001.ant.amazon.com (10.43.161.207) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 16 Dec 2020 23:28:59 +0000 Received: from EX13MTAUWA001.ant.amazon.com (10.43.160.58) by EX13D02UWB003.ant.amazon.com (10.43.161.48) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 16 Dec 2020 23:28:59 +0000 Received: from dev-dsk-vcchunga-2a-c5-3b7a0bed.us-west-2.amazon.com (172.19.55.163) by mail-relay.amazon.com (10.43.160.118) with Microsoft SMTP Server id 15.0.1497.2 via Frontend Transport; Wed, 16 Dec 2020 23:28:59 +0000 Received: by dev-dsk-vcchunga-2a-c5-3b7a0bed.us-west-2.amazon.com (Postfix, from userid 6361087) id 5C9B9AE332; Wed, 16 Dec 2020 15:28:59 -0800 (PST) From: Vimal Chungath To: CC: , , , , , , , , , , Date: Wed, 16 Dec 2020 15:28:57 -0800 Message-ID: <20201216232857.9033-1-vcchunga@amazon.com> X-Mailer: git-send-email 2.16.6 In-Reply-To: <1605874101-30893-1-git-send-email-juraj.linkes@pantheon.tech> References: <1605874101-30893-1-git-send-email-juraj.linkes@pantheon.tech> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH v13 00/12] Arm build options rework 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 11/20/20 4:08 AM, Juraj Linkeš wrote: > The current way of specifying Arm configuration options is insufficient > since we can't identify the SoC we're building for from the MIDR > information. For example, we can't distinguish between N1SDP, Graviton2 > or Ampere Altra. > > Add a way to specify the cpu count and numa node count for cross builds > and aarch64 -> aarch64 (SoC) builds. > > We also want to be able to disable which drivers (and possibly > libraries) are built without user input. This is useful when building: > 1. on an SoC that is slow and we want to build only what is necessary > without the user having to check which libraries they have installed > 2. a cross build on a fast aarch64 machine but with target SoC which > differs in capabilities or libraries. > This is achieved by specifying the drivers in SoC configuration. > > Among libraries, only libnuma can be now disabled. > > Also add an optional way to discover cpu count a numa node count. Fix > -Dmax_lcores and -Dmax_numa_nodes for arm builds. > > The current implementation adds/supports the following: > * x86 -> aarch64 cross build with added config options/disabled > drivers/libs > * aarch64 -> aarch64 builds for a different SoCs using meson -Darm_soc > option or using a cross file > * max numa nodes and max lcore may be specified on the command line to > overwrite the values for any (native, SoC or cross) build > I tested on Graviton2 and it looks good to me. I tested native, cross and the arm_soc builds and verified the config options for Graviton2. Series Tested-by: Vimal Chungath