| Message ID | 20240321184721.69040-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 78C5C43D0F; Thu, 21 Mar 2024 19:48:05 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B205A42E4C; Thu, 21 Mar 2024 19:48:02 +0100 (CET) Received: from NAM12-MW2-obe.outbound.protection.outlook.com (mail-mw2nam12on2089.outbound.protection.outlook.com [40.107.244.89]) by mails.dpdk.org (Postfix) with ESMTP id 22C4F42E4C for <dev@dpdk.org>; Thu, 21 Mar 2024 19:48:01 +0100 (CET) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZksftC+PnYQFcyPBqGrL8N7QXqXSazfPKH2hq+HeE+AnQ7AGue4yz2DFbQdFBzq5mtTuhKSZA7tgeaQv17MTN2qpGK4GzmqlQxY6rm1oFbQnfq6fWkTrQbzAZHpOS84UelU2MGtRZUEDIUhJUfjCRWsmZRRqyZ0XOl2mHsF0Mmldd6GVKh/OUjRbwt0dZRxoDq7zrJH6tsilWn/jDRw6CURlQElTHMD+6JlMBiyp0My5xB8W8T07JH4GK4q4VD47QGCW8dI8NU/Y2toUhyvfQiMigC8eWDw2RxWwL9P0IqnGKsDwYbWlCa0jOumVM4Vxq1nxRiLstVQzWyP5EnxUzA== 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=hAOBPIWlWD0YjXwjDhiIiCAbPUHI5S5Pi9mw8CM8lHU=; b=e2eHeoEs9K2S4Me3f0VO+a7g+5iUczmjyPQG6oSDizqywI2rBopkPq04Utj1sxpCpd7bPzDgcHX4dJ7LopJCfI3EWyXlJ2VH+2mZPX6XrF4k7SDpUxeAcaonZK3JLculY9C/7yRbjkNIcp66CvgFFuow7dT7LDDCcTVnsGiCncmtai66QxU9HA4rdEACUotHQsqR7n4C4cIBdGY/wtht658a6LNmW4LrusMpWLZoCQHS848B7oVJLlvycwx5e+ffTgtpUe2URDKNDUUye7l3QTElZIBVO6IXGjeNyz0meqMZdcOGaSjdmmf604En3qXeATMgrrhNSVEEGOWTcQiRLg== 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=hAOBPIWlWD0YjXwjDhiIiCAbPUHI5S5Pi9mw8CM8lHU=; b=eZIGVuF8gHGrInAA+oxyy4HOLCGV7d9j7UNcn/ku9+yvAxL1j7S8gd1fqpaxpNXVZCbe45grNPubMuU9ipDQWx250aZ9k9RR6TThSS03mspe6MYouY5Z9PMDqzrFKtMPXJyDUM3MgAU+mrjOGPmoHEqlFUt/azLPlp9E4g8T4ZI= Received: from BL0PR02CA0124.namprd02.prod.outlook.com (2603:10b6:208:35::29) by PH0PR12MB8006.namprd12.prod.outlook.com (2603:10b6:510:28d::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7362.24; Thu, 21 Mar 2024 18:47:49 +0000 Received: from BL6PEPF0001AB75.namprd02.prod.outlook.com (2603:10b6:208:35:cafe::63) by BL0PR02CA0124.outlook.office365.com (2603:10b6:208:35::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7386.27 via Frontend Transport; Thu, 21 Mar 2024 18:47:49 +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 BL6PEPF0001AB75.mail.protection.outlook.com (10.167.242.168) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.7409.10 via Frontend Transport; Thu, 21 Mar 2024 18:47:48 +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; Thu, 21 Mar 2024 13:47:42 -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>, <mb@smartsharesystems.com>, <thomas@monjalon.net> CC: <dev@dpdk.org> Subject: [PATCH v6 00/10] fix lcore ID restriction Date: Thu, 21 Mar 2024 19:47:06 +0100 Message-ID: <20240321184721.69040-1-sivaprasad.tummala@amd.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20240318173146.24303-1-sivaprasad.tummala@amd.com> References: <20240318173146.24303-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: BL6PEPF0001AB75:EE_|PH0PR12MB8006:EE_ X-MS-Office365-Filtering-Correlation-Id: 2004f200-939e-4b97-5dac-08dc49d76824 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: ptANxuCQaSuMcFBFKwJhxHrK/OP1xbkmljs9Iwm7hea5aIR2QshGmF768jCjM8SF4fkjXuvRoDJ2mRz9Qbf0fP4cRDZ94oZ3+QgF0maeiknRPxZemrCSsTuqhx/P0UfMi76qBNR0MOvr/tHPhPBCBmL52c8L8N/L7SsmKQkclgxq5ywF0IT8H2uaqQhIz0xpkVFT6FnieKyF56xcGHqJUVOv84W6+AIjBmBikBh9CWXZiYZv7GhBU46rus/jtXA8ZU0PGasZxx/x9HYztnpkJyrJodvBIkWU+aEjOn+Le0s1vVDC7UsbJseGJXVaOyM6+NQyFZHHBZlO62RdfV6CUpbfF0tj79sYv4MAVK8luiWNU0PXoysjf30/zheQt9EjzDurGVk2tlvXteeh4REmkGENalXpAthfpGfe+ob8007fJmJc5wu/Xreyh62F/BOWsqiOkwYO7WRoaKG5Im011Vlb+IEAVQZqHblFtyS/OJgWRdkyjwyiCzqe0CSpXm90CwOiBK/uu6OPZ2PJ29SvF2UonawbrEpZeBQoYqZdehuesV6OvG62vmSiPlKeltFz9hLgxlkvdf1nApZxPLeHHy8T7sdoCVtrhMwJkGVyt/v4AbEe3aBaOjkRtKNjzZBf6SoCgcvBcY3B8LM9Vs0oWum1hpqQIOZbfIaGbyXyWL0j8z8i85KF3qEFn+OPbcbcT1PFds4DLJ3eLcNrErdruOZ4AmZnotLIVXVcdJ4dWGrzqdwmXSSJMb6f//KPt27KFl34wQ7m9tQgAtF7tgXQaw== 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)(36860700004)(82310400014)(376005)(7416005)(1800799015)(921011); DIR:OUT; SFP:1101; X-OriginatorOrg: amd.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Mar 2024 18:47:48.8934 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 2004f200-939e-4b97-5dac-08dc49d76824 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: BL6PEPF0001AB75.namprd02.prod.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH0PR12MB8006 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 21, 2024, 6:47 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. The port ID constraints were also fixed to support up to RTE_MAX_ETHPORTS. v6: - split queue_id, lcore_id and port_id changes as separate patches. - updated git commit description on individual patches 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 (10): examples/l3fwd: fix queue ID restriction examples/l3fwd-power: fix queue ID restriction examples/l3fwd-graph: fix queue ID restriction examples/ipsec-secgw: fix queue ID restriction 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 | 31 +++++----- examples/l3fwd-power/main.c | 59 +++++++++---------- examples/l3fwd-power/main.h | 4 +- examples/l3fwd-power/perf_core.c | 14 +++-- 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 | 38 ++++++------ examples/qos_sched/args.c | 6 +- .../guest_cli/vm_power_cli_guest.c | 4 +- 18 files changed, 119 insertions(+), 113 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. The port ID constraints were also fixed to support up to RTE_MAX_ETHPORTS. v6: - split queue_id, lcore_id and port_id changes as separate patches. - updated git commit description on individual patches 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 (10): examples/l3fwd: fix queue ID restriction examples/l3fwd-power: fix queue ID restriction examples/l3fwd-graph: fix queue ID restriction examples/ipsec-secgw: fix queue ID restriction 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 | 31 +++++----- examples/l3fwd-power/main.c | 59 +++++++++---------- examples/l3fwd-power/main.h | 4 +- examples/l3fwd-power/perf_core.c | 14 +++-- 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 | 38 ++++++------ examples/qos_sched/args.c | 6 +- .../guest_cli/vm_power_cli_guest.c | 4 +- 18 files changed, 119 insertions(+), 113 deletions(-)