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 50F99A04E7; Tue, 3 Nov 2020 19:53:15 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 985154CA6; Tue, 3 Nov 2020 19:53:13 +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 000BB4C96 for ; Tue, 3 Nov 2020 19:53:10 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1604429592; x=1635965592; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=tLFUMzfm3up6S2ATr1tVGxuc5SA44WfbwjUE157+6ZM=; b=UkfGyvhhi3spersi15NthHwotYC4RMSUS2l+WXDwL2DHf1CDGOzCwAy5 LBo97DrO3eXDpXuJt1Y64TpMhX2gchUX8V7sHRkYlYFA5t5MKFpikM1D4 TRlpYE+kHOb8lnxRmDd8x2nuwctYPyo7Wn76PwUWO68ivo6/SF1iW3BF6 4=; X-IronPort-AV: E=Sophos;i="5.77,448,1596499200"; d="scan'208";a="62194759" Received: from iad12-co-svc-p1-lb1-vlan3.amazon.com (HELO email-inbound-relay-2c-4e7c8266.us-west-2.amazon.com) ([10.43.8.6]) by smtp-border-fw-out-2101.iad2.amazon.com with ESMTP; 03 Nov 2020 18:52:19 +0000 Received: from EX13MTAUWB001.ant.amazon.com (pdx1-ws-svc-p6-lb9-vlan2.pdx.amazon.com [10.236.137.194]) by email-inbound-relay-2c-4e7c8266.us-west-2.amazon.com (Postfix) with ESMTPS id B1E7CA2C03; Tue, 3 Nov 2020 18:51:35 +0000 (UTC) Received: from EX13D02UWB004.ant.amazon.com (10.43.161.11) by EX13MTAUWB001.ant.amazon.com (10.43.161.207) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 3 Nov 2020 18:51:15 +0000 Received: from EX13MTAUWA001.ant.amazon.com (10.43.160.58) by EX13D02UWB004.ant.amazon.com (10.43.161.11) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 3 Nov 2020 18:51:14 +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; Tue, 3 Nov 2020 18:51:14 +0000 Received: by dev-dsk-vcchunga-2a-c5-3b7a0bed.us-west-2.amazon.com (Postfix, from userid 6361087) id C0C05BED07; Tue, 3 Nov 2020 10:51:14 -0800 (PST) From: Vimal Chungath To: CC: , , , , , , , , , , Date: Tue, 3 Nov 2020 10:51:13 -0800 Message-ID: <20201103185113.3262-1-vcchunga@amazon.com> X-Mailer: git-send-email 2.16.6 In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [dpdk-dev] [PATCH v3 1/1] build: add Graviton2(arm64) meson configuration 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/3/20 10:38 AM, Jerin Jacob Kollanukkaran wrote: > > >> -----Original Message----- >> From: Thomas Monjalon >> Sent: Wednesday, November 4, 2020 12:02 AM >> To: Vimal Chungath ; >> honnappa.nagarahalli@arm.com; Dharmik.Thakkar@arm.com; Jerin Jacob >> Kollanukkaran ; juraj.linkes@pantheon.tech >> Cc: dev@dpdk.org; alisaidi@amazon.com; bruce.richardson@intel.com; >> hemant.agrawal@nxp.com; jerinjacobk@gmail.com; nd@arm.com >> Subject: [EXT] Re: [PATCH v3 1/1] build: add Graviton2(arm64) meson >> configuration >> >> External Email >> >> ---------------------------------------------------------------------- >> 03/11/2020 19:06, Vimal Chungath: >>> Add meson build configuration for Graviton2 platform with 64-bit Arm >>> Neoverse N1 cores. This patch makes the following changes to generic >>> Neoverse N1 config: >>> >>> 1. increase lcore limit to 64 >>> 2. increase memory support to 1TB >>> 3. remove +crc from -march as that is default when setting armv8.2 >>> >>> Signed-off-by: Vimal Chungath >>> --- >>> config/arm/arm64_graviton2_linux_gcc | 17 +++++++++++++++++ >>> config/arm/meson.build | 18 +++++++++++------- >>> 2 files changed, 28 insertions(+), 7 deletions(-) >> >> Can this patch be merged without the rework from Juraj? > > Yes. +1 > > @Vimal Chungath, Could you review and test Juraj changes on Graviton2 so that > Juraj changes can be targeted for 21.02. > Yes, will do that.