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 F1DCFA051F for ; Wed, 10 Jun 2020 15:38:49 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D6D141B53; Wed, 10 Jun 2020 15:38:49 +0200 (CEST) Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2049.outbound.protection.outlook.com [40.107.243.49]) by dpdk.org (Postfix) with ESMTP id 70421F04; Tue, 9 Jun 2020 18:30:10 +0200 (CEST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hta2icBWeBg7fLCYlhVpj4LH62D2k1kpeczyW6euZ3/3an7jJVN2bgblgP7w4Jw6vSlcxtZSXDUWweELqWaHc++yL7xBuaIkE17WFvFgD3O8FTK+xWBbXXA/ChQu3DW2pCU1iUg6wbPZNqTNmWiYRfg9wtk9TEIejmiZx5npQR9hMOEXJXPJWrCfmIjyx2Mz2BD+h5+hCZBzgQB7e4VR1zS4zmIclWVhXIlm1ivc/Jb8d0vvADmdzz/bDzoQFWPJyPHWECURlW5PySzdoe9mNmbbdQQ3jy+7jO7hcH+/O3SC6Z0z4iJ7SIj9w+47XXP/Ln95E+XzGNlCg5feK/OORg== 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=5L1GRdWOANCBdLkGZHknVa3iHP0dVDXBvZI/lpMmNLU=; b=JATzSse8QFrl8TA4MX8c5yDD3Rq4N/Y+CPBSEUEKShyvnP3LLbNXYHI9rPFKBIQ7tiukCZkd3E/HbEfIGHRRuxFAozL+0DCAWu4xkH3LwPx61dAui2G7Z7/3NkwJf2XxlVlmwlqry/TyLbGuGw7HruX40s6fonsNbjmjAG35hWyqofOguyvH9Nnh7f1EUaENyR3sQmsDHR+K480e2yWoUNFQTfACYTOq89+ZlorQLz59YeU3xMo6NJOzxKRMkH+NrqU/Y5yhD0eAIxTe3PKI7ZbfSG5vZjwzIPfLKgEXSeNwqOWd0F5oYP6XLfFF19EtXt/jfK5BXAKT5JUQc6WwmQ== 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=5L1GRdWOANCBdLkGZHknVa3iHP0dVDXBvZI/lpMmNLU=; b=gFKxT2stvbkf1HwS0KB3KSxRWpfqDwhfcfVtkYWyWIcrVJxmb2jtXaF7RG/m+H5a9n7EuddkhYuurvWx6RXeeVkEOhRgr+l27PKZDZfhLOm6gxsZ+KERKXBfhFBgQeSTe5v0+aIS4NI34HJ91I3mMFK+gdyf2wlDDelEDuQZYMo= Received: from BY5PR12MB3681.namprd12.prod.outlook.com (2603:10b6:a03:194::16) by BY5PR12MB3860.namprd12.prod.outlook.com (2603:10b6:a03:1ac::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3066.18; Tue, 9 Jun 2020 16:30:06 +0000 Received: from BY5PR12MB3681.namprd12.prod.outlook.com ([fe80::a8e3:8029:c45c:e47b]) by BY5PR12MB3681.namprd12.prod.outlook.com ([fe80::a8e3:8029:c45c:e47b%3]) with mapi id 15.20.3088.018; Tue, 9 Jun 2020 16:30:06 +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++YeQgAABZcCABemWAIAADi7QgAwxLWA= Date: Tue, 9 Jun 2020 16:30:06 +0000 Message-ID: References: <20191202153559.9709-1-david.marchand@redhat.com> <3762540.mo1vFcNuoO@thomas> In-Reply-To: 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-09T16:30:04Z 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: 59f52005-5b77-4c57-ba2b-0000b165b646 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: [165.204.78.25] x-ms-publictraffictype: Email x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: ec8b5d59-09b4-46b4-b6b4-08d80c925ebf x-ms-traffictypediagnostic: BY5PR12MB3860: x-ms-exchange-transport-forked: True x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-forefront-prvs: 042957ACD7 x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: TxDcyA8LoOBMQyjdkHOlFFIxeK/SJcKkA7dKUBTSDl21fBu2zwb4XsB2pj/kIC+cG8bgl1SzWyAiIUaabvj/k0fSvOGSBY3hB0IwMgjfTLNSAumwIWVVLd48ghjGCkbIhBjBJ/ET6se7gqdRFi5HIiTaD72Ky0srxlnlSE2KajYSIAprz84J+U7tFQU5D9BVJhZ9DrrtQOqjfxDG0PFhLHqBjM/cLrSxMLSbkhbdEXDnhjJkzyDiqbVnfciVIKD4YXpc9xnF0xKdVTcn/5N2j3hA4sbFrPvoOM47h6PJY3UBZRgxqCQPowINMWbdKYnwesbFoACK8oH+lD8PAOorjP8KqgteaH9tpZH4ioAW/xh9WUJnAnChGchqq5kqsU/gLe5kI33t8XXDZmdZf9EuCw== 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)(396003)(136003)(346002)(376002)(52536014)(9686003)(8936002)(66446008)(66946007)(5660300002)(76116006)(66476007)(64756008)(8676002)(186003)(53546011)(66556008)(26005)(86362001)(55016002)(2906002)(316002)(54906003)(83380400001)(33656002)(966005)(478600001)(6506007)(4326008)(6916009)(45080400002)(7416002)(71200400001)(83080400001)(7696005); DIR:OUT; SFP:1101; x-ms-exchange-antispam-messagedata: GVZtG5PTpWgF+3ibcBrXz9lwwinyeyQmQ7JJSiqutjqo0E/AanYhTU2I/068w5wRl/rDl1mJfQABctcgGxkU66dMxAVam9PvfyjY8/Jd9fXEY7hQToU9dzKq52yXJvDlqTUwbQcYAbhtOliZXL5pQeR3hN+R9bZBA6rGMaQhv4+EkKbTKAu5yfK4wwKvxnZeMFwCdqD8snCSfCpTUAKFtpqW2FlsMrWh823uieDdZyQQ76LAxNrdv2tiVLDdOQoNJGDXfBMOR+gGsRvSeJobIgDkNNXtkSAr/xs+V5KkY6PPPXcoK8N8YE8kqH9q0ez2EstXhnvQ8t1bRSSNYDBQbIsv1o5BYEtY/jKnGHNUtC838xPlG9/qcbmgRFRrdbJ0XIS+Fyyr3wVXFB97vecHJb6z1EGtywP6R9ENOGpuzreF/eLMOKKuC5nOszNfDxmJTH2J6ZjRHWAYWTmqbmGeBWWaoT6HqJmRTXjn9d92VCo= 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: ec8b5d59-09b4-46b4-b6b4-08d80c925ebf X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jun 2020 16:30:06.6146 (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: IcddHNXDADQ9jByd//QOEW5FH/MexA9SZ/JRGPehNjFrFA8r3wpsiriQqkmEnoU9FQgutWPpdBbVcg1DvFpbtA== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR12MB3860 X-Mailman-Approved-At: Wed, 10 Jun 2020 15:38:48 +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] Hi Kevin and Luca, We are still waiting for the response. Can you help on this for the backports in 18.11 and 19.11? It would work for our customers even with changing the default value of ' C= ONFIG_RTE_MAX_LCORE' to 256 in common_base file in 18.11 and 19.11. Thanks, Keesang -----Original Message----- From: Song, Keesang=20 Sent: Monday, June 1, 2020 3:54 PM To: Thomas Monjalon 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; Aman Kumar ; Grimm, Jon Subject: RE: [dpdk-dev] [PATCH 0/4] Extend --lcores to run on cores > RTE_M= AX_LCORE [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 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?