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 3C429A04F5 for ; Sat, 6 Jun 2020 22:03:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5F77E1C220; Sat, 6 Jun 2020 22:03:35 +0200 (CEST) Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2069.outbound.protection.outlook.com [40.107.220.69]) by dpdk.org (Postfix) with ESMTP id CC06A1BFE3; Tue, 2 Jun 2020 00:54:12 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=F4AJ+5AwU+sIQFHNCphXXX1EvlDy4NXphrPRHrlM0WAE3XA9uAqnRmnRVPAL3QEJ5J4bS8ONptQvkzmT9ttoynP1cnBnli5vdw9yjnH2OIZaxseU/3Am2DN+rpbDfxkfkpUNWP1LTpxRNQCHHCpPhMGWzbjCaq8OUZg5ibnof/lk8/jvMKZUM/WBN4Vt+n4I9lUBFYzSszA706v4DMOLwX1X3IViDuoaG49HJdqOTgB+2caeyug2iMDc2l0QyVpb2J2di4m4tCnt37F/WQkQ9FWDmyIvgy6Iq/7GdO4QBUyncv7RMOCgd2CFE+bBls5nBB/adk6+URx/96Kfs5+hfg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kVKkBntg5fTQmssK36j+/jxtNYVfdQTF6v9AcKFmsBg=; b=Jy/e1nZ3R1aZpKxdwrP91lBMMCGFce9Zpe2abM2Jni4BD3Wqx1Yo2nYZF+l7cvy0MNT+bYHM5gnB0gbGnR6DuhzBUPQW2utelo7WibDB4jozOMEhusKgJ1gfsagdmhIBNcYYRXCDewyF01S8G5ZFq3H/kzPTvVNAq6GODPd87imzHG8IIOfkf6furSB38D9VW1zzd12xKkUF4nBiWbSYkvuWt6NzUyNIIUs2P18tj6ItHm36z/x4yesBn+V06WNz60Ym6Aw4Lxj2ZB/07sHTaNZutwpjqNyATsqMcDT5gpk4gUFPL6VX+YocUaoHNjPsLLIC5l4X0Lw9+p4CvW6SzQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=amd.com; dmarc=pass action=none header.from=amd.com; dkim=pass header.d=amd.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amdcloud.onmicrosoft.com; s=selector2-amdcloud-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kVKkBntg5fTQmssK36j+/jxtNYVfdQTF6v9AcKFmsBg=; b=mwzt9xQr+8bKveak2u+8o5GRHX11qAaR3/LSBEK9OpXHcaOoM7wwG+vgyTBHwrhtgcpsmXlxVWqFRuJmuRHI1BDACsiq4Z/5hoeZGY56wrVZe5tJGUCU2FZJIGNS4Jal0h28m/XpNY7JisYZNSNq+BMuEBR1dUjbg7JpTb/5kaY= Received: from BY5PR12MB3681.namprd12.prod.outlook.com (2603:10b6:a03:194::16) by BY5PR12MB3955.namprd12.prod.outlook.com (2603:10b6:a03:1a2::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.17; Mon, 1 Jun 2020 22:54:10 +0000 Received: from BY5PR12MB3681.namprd12.prod.outlook.com ([fe80::78d1:212f:dc85:f25]) by BY5PR12MB3681.namprd12.prod.outlook.com ([fe80::78d1:212f:dc85:f25%5]) with mapi id 15.20.3045.024; Mon, 1 Jun 2020 22:54:09 +0000 From: "Song, Keesang" To: Thomas Monjalon CC: David Marchand , "dev@dpdk.org" , "aconole@redhat.com" , "ferruh.yigit@intel.com" , "bluca@debian.org" , "ktraynor@redhat.com" , "bruce.richardson@intel.com" , "honnappa.nagarahalli@arm.com" , "drc@linux.vnet.ibm.com" , "stable@dpdk.org" , Aman Kumar , "Grimm, Jon" Thread-Topic: [dpdk-dev] [PATCH 0/4] Extend --lcores to run on cores > RTE_MAX_LCORE Thread-Index: AQHV6I2IX5PZPP4EVkOqG56J+9A5iKi++YeQgAABZcCABemWAIAADi7Q Date: Mon, 1 Jun 2020 22:54:09 +0000 Message-ID: References: <20191202153559.9709-1-david.marchand@redhat.com> <3762540.mo1vFcNuoO@thomas> In-Reply-To: <3762540.mo1vFcNuoO@thomas> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_0d814d60-469d-470c-8cb0-58434e2bf457_Enabled=true; MSIP_Label_0d814d60-469d-470c-8cb0-58434e2bf457_SetDate=2020-06-01T22:13:47Z; MSIP_Label_0d814d60-469d-470c-8cb0-58434e2bf457_Method=Privileged; MSIP_Label_0d814d60-469d-470c-8cb0-58434e2bf457_Name=Public_0; MSIP_Label_0d814d60-469d-470c-8cb0-58434e2bf457_SiteId=3dd8961f-e488-4e60-8e11-a82d994e183d; MSIP_Label_0d814d60-469d-470c-8cb0-58434e2bf457_ActionId=02de1e13-2b21-421c-9c4c-0000338cf4ff; MSIP_Label_0d814d60-469d-470c-8cb0-58434e2bf457_ContentBits=1 msip_label_0d814d60-469d-470c-8cb0-58434e2bf457_enabled: true msip_label_0d814d60-469d-470c-8cb0-58434e2bf457_setdate: 2020-06-01T22:54:08Z msip_label_0d814d60-469d-470c-8cb0-58434e2bf457_method: Privileged msip_label_0d814d60-469d-470c-8cb0-58434e2bf457_name: Public_0 msip_label_0d814d60-469d-470c-8cb0-58434e2bf457_siteid: 3dd8961f-e488-4e60-8e11-a82d994e183d msip_label_0d814d60-469d-470c-8cb0-58434e2bf457_actionid: cc338544-a297-42be-93e1-0000343d7400 msip_label_0d814d60-469d-470c-8cb0-58434e2bf457_contentbits: 0 authentication-results: monjalon.net; dkim=none (message not signed) header.d=none;monjalon.net; dmarc=none action=none header.from=amd.com; x-originating-ip: [2600:1702:4a0:2e10:7c97:2c36:e13f:27e4] x-ms-publictraffictype: Email x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: 2c7d0d4e-8c86-4e32-9e4a-08d8067eb246 x-ms-traffictypediagnostic: BY5PR12MB3955: x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:4125; x-forefront-prvs: 0421BF7135 x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: hYV4WmkTkMVvJE3+SmVCama3FV7os4lxr2W71VhnVV/VwMPUJmk6xzyAv5+MZ6cLOwSO7WuB7aDgeWkicEW4JNJyNRuKbdgHXBNqO1LvDM4g9n+PYTo1Zb9qMNkl6JaQNHvAlrfTjmy1xZDhKzaBYdGVu3vlKJBinemO3ap62/zKRA1O6P68DxMvItbWJBKLXgJCXuV6MMJdLzj9/4xVhR8bKoKuV6rkBi2erKFvofU0Y78cdEdLMyVOK9md9d7YN7N0EfnG44E0JtsZoAT7HKX/9GiyDl6CeIL6KodnKROvEYLlqNzTUkO1gO7YT44+6S5Fj48G+tzYmc+09Mr1rEyAPDJ4rz7l5Bu+SJyM2sxqhzMFH5nFnBJAb9tXQZ3Fu8Xot0Fgr5VIa32dQx7M0A== x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BY5PR12MB3681.namprd12.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(366004)(39860400002)(346002)(396003)(376002)(136003)(66446008)(66556008)(64756008)(2906002)(52536014)(66476007)(8936002)(6916009)(316002)(7416002)(76116006)(54906003)(66946007)(83080400001)(83380400001)(186003)(55016002)(45080400002)(5660300002)(71200400001)(7696005)(966005)(478600001)(4326008)(86362001)(9686003)(6506007)(53546011)(8676002)(33656002); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata: o+QZKhFAPk+omRJnp3Qann9PPZhOk+12WpGjlrdFew613Hv6Nn8mYfOGt4IgrtbjMJDrZV0W+33gqjlhGMq+t0cjWHvYdrHVx1dFIwYmdrL9meYphb8fduSFhdOhzCVjDX7UKQTRaog/VBDt2WTlbo7vxYiF3lh36sN5kABV6DQvs9iZpGvMeFvTVuIy3TC3zpH9xXt9Rga/d0I5JAMtGO9Wgdacy0zXX7g+KWJCBPaUBtnzscYOm5zkBx86S/AlOIOJM2az41dMw6eK1hAFsQxj22000OXubMbTFRihiGFMAg0kdccCvIeFNzjrECAmfXOjp+x2sWpZnTo1cG2eSRg8eZ0qTLrlNCUSL1empEFPtFPNWRgb0ScwEx387sAmxj/TImJEhYpgLfoZZKobK5DxGO3dH3iN2lu7W5LvSvOmwB0caj6KIJm9ph9I7dbAHEnsDjLJXJh0gQKqsanXiqM+j0BYF73sX0tL7iu9KURKpe0/EFwsuynDH1q5RLBy3EtcjPM3R3/z4wiyanNJSPoO3KKA9N5B2BuVl/SNOF53ItGCrzZDsd3irozIAkrB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: amd.com X-MS-Exchange-CrossTenant-Network-Message-Id: 2c7d0d4e-8c86-4e32-9e4a-08d8067eb246 X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Jun 2020 22:54:09.8494 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 3dd8961f-e488-4e60-8e11-a82d994e183d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: wIjfwVqqFzebKR/U+TWO6q5+U8iPNgqYdnAsgTvRGP/vpSHoghnN/dOfKhMgLK8hkWwCZnl4QMkqZzPYr7LEKw== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR12MB3955 X-Mailman-Approved-At: Sat, 06 Jun 2020 22:03:33 +0200 Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 0/4] Extend --lcores to run on cores > RTE_MAX_LCORE X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" [AMD Public Use] Thanks Thomas for the response. For a correction, the patchwork has not been submitted for the current LTS = release, 19.11.2, but was merged into 20.02 and onward.=20 The reason I brought this again was to address LTS users and many other app= lication based on the LTS releases(18.11 & 19.11). Since I found many of our customers and users are still relying on the late= st LTS version, I'm seeking an aid for adding this change into at least 19.= 11, LTS branch. We could argue that this is actually not a bug, in a way, it's inconvenient= for Openstack or cloud deployed DPDK application since it's often inapt to= change the base config and recompile the max lcore limit. If backporting is still not a preferred way(pushing this patchwork into 19.= 11), then can we instead consider changing only the default value of ' CONF= IG_RTE_MAX_LCORE' to 256 in common_base file? # Compile Environment Abstraction Layer # CONFIG_RTE_MAX_LCORE=3D128 --> 256 I'd appreciate if anyone can advise me know what we can do about this to mo= ve forward. -----Original Message----- From: Thomas Monjalon =20 Sent: Monday, June 1, 2020 2:23 PM To: Song, Keesang Cc: David Marchand ; dev@dpdk.org; aconole@redha= t.com; ferruh.yigit@intel.com; bluca@debian.org; ktraynor@redhat.com; bruce= .richardson@intel.com; honnappa.nagarahalli@arm.com; drc@linux.vnet.ibm.com= ; stable@dpdk.org Subject: Re: [dpdk-dev] [PATCH 0/4] Extend --lcores to run on cores > RTE_M= AX_LCORE [CAUTION: External Email] 29/05/2020 05:05, Song, Keesang: > Hi Thomas & David, > > We haven't got the final status on this patch, and I don't see this chang= e even from the latest LTS 20.04 repo. > So I'd like to confirm whether this patch has been safely submitted to th= e main upstream. > Can you check the status of that commit? > > https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fpatc > hwork.dpdk.org%2Fpatch%2F63507%2F&data=3D02%7C01%7CKeesang.Song%40am > d.com%7Cd71ea9aca917447dfb3e08d80671f34c%7C3dd8961fe4884e608e11a82d994 > e183d%7C0%7C0%7C637266433776198364&sdata=3D1EgxevCILVMMLgyQC%2FzaWYJ > XJ%2BOijs0Rtym1TA0VS28%3D&reserved=3D0 As you can see below, there is a pending question: "is it a new feature or a fix?" Kevin and Luca are the arbiters for the backports in 18.11 and 19.11. > -----Original Message----- > From: Thomas Monjalon > Sent: Friday, February 21, 2020 12:04 AM > > Hi, > > 21/01/2020 01:24, Thomas Monjalon: > > 02/12/2019 16:35, David Marchand: > > > We are currently stuck with no option but recompile a DPDK if the=20 > > > system has more cores than RTE_MAX_LCORE. > > > A bit of a pity when you get a system with more than 200+ cores=20 > > > and your testpmd has been built and packaged with RTE_MAX_LCORE =3D= =3D 128. > > > > > > The --lcores does not need to care about the underlying cores,=20 > > > remove this limitation. > > > > > David Marchand (4): > > > eal/windows: fix cpuset macro name > > > eal: do not cache lcore detection state > > > eal: display all detected cores at startup > > > eal: remove limitation on cpuset with --lcores > > > > The patches look good but it is very hard to review parsing code (last = patch). > > We will better experience corner cases after merging. > > > > Applied for -rc1, thanks > > This patch was merged in 20.02. > We don't have any feedback about issues so it's probably working fine. > > It is solving a problem for running DPDK on machines having a lot of core= s. > Now the difficult question: is it a new feature or a fix? > Should we backport this patchset?