| Message ID | 20240318173146.24303-1-sivaprasad.tummala@amd.com (mailing list archive) |
|---|---|
| Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6E4E843CE8; Mon, 18 Mar 2024 18:32:24 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 68EEC406A2; Mon, 18 Mar 2024 18:32:17 +0100 (CET) Received: from NAM11-DM6-obe.outbound.protection.outlook.com (mail-dm6nam11on2073.outbound.protection.outlook.com [40.107.223.73]) by mails.dpdk.org (Postfix) with ESMTP id 0863640696 for <dev@dpdk.org>; Mon, 18 Mar 2024 18:32:16 +0100 (CET) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=B8LeNMvpiMtnjCEPz+qrFUgZpRSCLkYtiM655fL05wY+LpDpi7cX5s0ExYQ34JLSBoWgV9voRj13lhT6TSsEBCnAHIdz36HpPbnnoQ6sksQ18xixsiiYZbvX74cg7tptw4O86Rl4YQQhE9TLaq6i3cGJHA8Z27wGyFHH89qc9mRD9sZOCD2bh/2MZqXglo05rKXFrmv9ZuxmOwU1WJPNZGxaApTV6Mwmz1eF/x0I1J9KAFIgkNNf18FjoTFE1TUzE/bXRUGZOPsC1nL8wQ6JrwwDHKN604SqDto4wVBM0MQ4i/pQ7KyMih1Ke5mlnPzUHwPME9ba6BYncAyELWKy7g== 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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=8YddQQvyN66HKTyeCpL8RkXuutu2IqchOLRutmVO0Gc=; b=mseUcTqN1ZfT3yWJHD2WGGtEOmpHSsHb0VS9Y8EQ9/Czs4uaJgPln6ffnX8CXRwDYjgaERt5hW2TciRPLEaCFc8w2diqbPID7OKxP1GVroQTW8isZt+763o7lv/KcI8UXxetDDs5bgjPQEtH/E1XZnG5Zb2UafpddhH+6iaNZSiFa4Yo8Mvs+hiU0X5UEFr85QuzT3y8rBVe/RcvTtzwxtjUgA3a3uHR1u8k4IJ4cQ+FbZH1t6I4I9R9xfU0++L1Q1cK1wek4AFLbqkaj25LZRu+kLAEwtrfcV4FQu9p26LhTAc9QoVYbg4QZO9eDTecI7ZnOiphO/wOSr8VuX0Zdg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 165.204.84.17) smtp.rcpttodomain=intel.com smtp.mailfrom=amd.com; dmarc=pass (p=quarantine sp=quarantine pct=100) action=none header.from=amd.com; dkim=none (message not signed); arc=none (0) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amd.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8YddQQvyN66HKTyeCpL8RkXuutu2IqchOLRutmVO0Gc=; b=sUWTBQhcrc2FK0NPEZ4aWbch46z6NfPOYhQwBTwRONeouOzQCcUThbB2PIV3eld4/YuQoItNx++6iwygkwu2+qv+IzqclvH6gPdkof+FvEYwIUrlR7mhdIq2ijYoCiJG7wjhYOxmT1D8tHEgcRreQaPPfFtvOmr4lgvbw08iFPU= Received: from DM6PR08CA0021.namprd08.prod.outlook.com (2603:10b6:5:80::34) by MN0PR12MB6125.namprd12.prod.outlook.com (2603:10b6:208:3c7::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7386.26; Mon, 18 Mar 2024 17:32:07 +0000 Received: from CH1PEPF0000AD7A.namprd04.prod.outlook.com (2603:10b6:5:80:cafe::34) by DM6PR08CA0021.outlook.office365.com (2603:10b6:5:80::34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7386.27 via Frontend Transport; Mon, 18 Mar 2024 17:32:07 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 165.204.84.17) smtp.mailfrom=amd.com; dkim=none (message not signed) header.d=none;dmarc=pass action=none header.from=amd.com; Received-SPF: Pass (protection.outlook.com: domain of amd.com designates 165.204.84.17 as permitted sender) receiver=protection.outlook.com; client-ip=165.204.84.17; helo=SATLEXMB04.amd.com; pr=C Received: from SATLEXMB04.amd.com (165.204.84.17) by CH1PEPF0000AD7A.mail.protection.outlook.com (10.167.244.59) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.7409.10 via Frontend Transport; Mon, 18 Mar 2024 17:32:07 +0000 Received: from ubuntu2004.linuxvmimages.local (10.180.168.240) by SATLEXMB04.amd.com (10.181.40.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Mon, 18 Mar 2024 12:32:03 -0500 From: Sivaprasad Tummala <sivaprasad.tummala@amd.com> To: <david.hunt@intel.com>, <anatoly.burakov@intel.com>, <jerinj@marvell.com>, <radu.nicolau@intel.com>, <gakhil@marvell.com>, <cristian.dumitrescu@intel.com>, <ferruh.yigit@amd.com>, <konstantin.ananyev@huawei.com>, <stephen@networkplumber.org>, <david.marchand@redhat.com> CC: <dev@dpdk.org> Subject: [PATCH v5 0/6] fix lcore ID restriction Date: Mon, 18 Mar 2024 18:31:39 +0100 Message-ID: <20240318173146.24303-1-sivaprasad.tummala@amd.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20240116182332.95537-1-sivaprasad.tummala@amd.com> References: <20240116182332.95537-1-sivaprasad.tummala@amd.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Originating-IP: [10.180.168.240] X-ClientProxiedBy: SATLEXMB03.amd.com (10.181.40.144) To SATLEXMB04.amd.com (10.181.40.145) X-EOPAttributedMessage: 0 X-MS-PublicTrafficType: Email X-MS-TrafficTypeDiagnostic: CH1PEPF0000AD7A:EE_|MN0PR12MB6125:EE_ X-MS-Office365-Filtering-Correlation-Id: b092d449-8919-4ef4-9c07-08dc4771557e X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: FpUK3lhw3VzC1tMSIwwT3k1M1N7tTbsCVdjWE+eZIbVTXCYtT/EqSPd9G2qMtAX5DRodbDDKusws13uGL6K0eX+U1i81mLT8HMMVvTelNP+k+CbHNNynF/90OuJrWzSTL3E6ilMmxuBMbcNe59WEmuLWWAOwCFNEFfr6rBVYqFlMUDT8W4DlA/q/Uup6+HBGrHmZ24cmaOShyIEXAlIaZCvyKUB3GK3JWsHVcXgUu86OdKn6QihgfU5EIVHsMsT7Aojg5UIwsJZuEekFuz92cEnHL56pRYWLN9/edvZs0LLqkeyDM0rH4EIDAaEx7utuVZMLAcju39pmnt2GHivi3sgcE2nGU6u0wAbJIIIFOIupuZ1qW/822L6jSCc+DXEOySmRxO3M73GHzUMClKDvGlE+IHjxh0j3d9H1mLJrrbKcAeCHIoD5ZcODW4HAhLVdl3GHISnrQB2S3ZRYt+V9zyLd9VrgcPgp2dDgMAdDNJZEUQ3EUYebIcYUWppRdzUT0RYrLo0STJX2LEHhIXuSyt8Qg1gJLIRF5AZuHomxX8juP7x7G0uF4/bv6cHWO7zxu1I6MhtmLL29gvoNxsYXfrl+vY/yIvdXki9r8x0hl00/q1xuYKDntnN9ZqsBjCMxWWARuWV7tGcTkjSAkbZgMaTjWamQIzNa+p/rP60gx+LOQUwh7QM1qntFTQbgNNmeyaSS6uTavBNzY6+mJK7jH/9AZSa0ZA9yDKlGZIVIRn7IHpb7hGazQaMWNGFR7+i1MoYOPNf291WjX8nLgt8vQg== X-Forefront-Antispam-Report: CIP:165.204.84.17; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:SATLEXMB04.amd.com; PTR:InfoDomainNonexistent; CAT:NONE; SFS:(13230031)(376005)(36860700004)(7416005)(1800799015)(82310400014)(921011); DIR:OUT; SFP:1101; X-OriginatorOrg: amd.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 Mar 2024 17:32:07.0380 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: b092d449-8919-4ef4-9c07-08dc4771557e X-MS-Exchange-CrossTenant-Id: 3dd8961f-e488-4e60-8e11-a82d994e183d X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3dd8961f-e488-4e60-8e11-a82d994e183d; Ip=[165.204.84.17]; Helo=[SATLEXMB04.amd.com] X-MS-Exchange-CrossTenant-AuthSource: CH1PEPF0000AD7A.namprd04.prod.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN0PR12MB6125 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org |
| Series |
fix lcore ID restriction
|
|
Message
Sivaprasad Tummala
March 18, 2024, 5:31 p.m. UTC
With modern CPUs, it is possible to have higher CPU count thus we can have higher RTE_MAX_LCORES. In DPDK sample applications, the current config lcore options are hard limited to 255. The patchset fixes these constraints by allowing all lcore IDs up to RTE_MAX_LCORES. Also the queue IDs are increased to support up to 65535. v5: - updated lcore_id type to uint32_t v4: - fixed build errors with queue_id type in ipsec-secgw v3: - updated queue_id type to uint16_t v2: - fixed typo with lcore_id type in l3fwd Sivaprasad Tummala (6): examples/l3fwd: fix lcore ID restriction examples/l3fwd-power: fix lcore ID restriction examples/l3fwd-graph: fix lcore ID restriction examples/ipsec-secgw: fix lcore ID restriction examples/qos_sched: fix lcore ID restriction examples/vm_power_manager: fix lcore ID restriction examples/ipsec-secgw/event_helper.h | 2 +- examples/ipsec-secgw/ipsec-secgw.c | 35 +++++------ examples/ipsec-secgw/ipsec.c | 2 +- examples/ipsec-secgw/ipsec.h | 6 +- examples/ipsec-secgw/ipsec_worker.c | 10 ++-- examples/l3fwd-graph/main.c | 33 ++++++----- examples/l3fwd-power/main.c | 59 +++++++++---------- examples/l3fwd-power/main.h | 4 +- examples/l3fwd-power/perf_core.c | 16 +++-- examples/l3fwd/l3fwd.h | 2 +- examples/l3fwd/l3fwd_acl.c | 4 +- examples/l3fwd/l3fwd_em.c | 4 +- examples/l3fwd/l3fwd_event.h | 2 +- examples/l3fwd/l3fwd_fib.c | 4 +- examples/l3fwd/l3fwd_lpm.c | 5 +- examples/l3fwd/main.c | 40 +++++++------ examples/qos_sched/args.c | 6 +- .../guest_cli/vm_power_cli_guest.c | 4 +- 18 files changed, 122 insertions(+), 116 deletions(-)
Comments
With modern CPUs, it is possible to have higher CPU count thus we can have higher RTE_MAX_LCORES. In DPDK sample applications, the current config lcore options are hard limited to 255. The patchset fixes these constraints by allowing all lcore IDs up to RTE_MAX_LCORES. Also the queue IDs are increased to support up to 65535. v5: - updated lcore_id type to uint32_t v4: - fixed build errors with queue_id type in ipsec-secgw v3: - updated queue_id type to uint16_t v2: - fixed typo with lcore_id type in l3fwd Sivaprasad Tummala (6): examples/l3fwd: fix lcore ID restriction examples/l3fwd-power: fix lcore ID restriction examples/l3fwd-graph: fix lcore ID restriction examples/ipsec-secgw: fix lcore ID restriction examples/qos_sched: fix lcore ID restriction examples/vm_power_manager: fix lcore ID restriction examples/ipsec-secgw/event_helper.h | 2 +- examples/ipsec-secgw/ipsec-secgw.c | 35 +++++------ examples/ipsec-secgw/ipsec.c | 2 +- examples/ipsec-secgw/ipsec.h | 6 +- examples/ipsec-secgw/ipsec_worker.c | 10 ++-- examples/l3fwd-graph/main.c | 33 ++++++----- examples/l3fwd-power/main.c | 59 +++++++++---------- examples/l3fwd-power/main.h | 4 +- examples/l3fwd-power/perf_core.c | 16 +++-- examples/l3fwd/l3fwd.h | 2 +- examples/l3fwd/l3fwd_acl.c | 4 +- examples/l3fwd/l3fwd_em.c | 4 +- examples/l3fwd/l3fwd_event.h | 2 +- examples/l3fwd/l3fwd_fib.c | 4 +- examples/l3fwd/l3fwd_lpm.c | 5 +- examples/l3fwd/main.c | 40 +++++++------ examples/qos_sched/args.c | 6 +- .../guest_cli/vm_power_cli_guest.c | 4 +- 18 files changed, 122 insertions(+), 116 deletions(-)
On 3/18/2024 5:31 PM, Sivaprasad Tummala wrote: > With modern CPUs, it is possible to have higher > CPU count thus we can have higher RTE_MAX_LCORES. > In DPDK sample applications, the current config > lcore options are hard limited to 255. > > The patchset fixes these constraints by allowing > all lcore IDs up to RTE_MAX_LCORES. Also the queue > IDs are increased to support up to 65535. > > v5: > - updated lcore_id type to uint32_t > > v4: > - fixed build errors with queue_id type > in ipsec-secgw > > v3: > - updated queue_id type to uint16_t > > v2: > - fixed typo with lcore_id type in l3fwd > > Sivaprasad Tummala (6): > examples/l3fwd: fix lcore ID restriction > examples/l3fwd-power: fix lcore ID restriction > examples/l3fwd-graph: fix lcore ID restriction > examples/ipsec-secgw: fix lcore ID restriction > examples/qos_sched: fix lcore ID restriction > examples/vm_power_manager: fix lcore ID restriction > For series, Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>