From patchwork Thu Mar 9 04:57:34 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Honnappa Nagarahalli X-Patchwork-Id: 124881 Return-Path: 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 3A48F41E2F; Thu, 9 Mar 2023 05:57:50 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D283940ED7; Thu, 9 Mar 2023 05:57:49 +0100 (CET) Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by mails.dpdk.org (Postfix) with ESMTP id 14A4F40A7E for ; Thu, 9 Mar 2023 05:57:48 +0100 (CET) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 01071C14; Wed, 8 Mar 2023 20:58:31 -0800 (PST) Received: from 2p2660v4-1.austin.arm.com (2p2660v4-1.austin.arm.com [10.118.14.10]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 615FE3F67D; Wed, 8 Mar 2023 20:57:47 -0800 (PST) From: Honnappa Nagarahalli To: mb@smartsharesystems.com, olivier.matz@6wind.com, konstantin.v.ananyev@yandex.ru Cc: dev@dpdk.org, honnappa.nagarahalli@arm.com, ruifeng.wang@arm.com, kamalakshitha.aligeri@arm.com, wathsala.vithanage@arm.com, nd@arm.com Subject: [PATCH 0/4] Small corrections in mempool Date: Wed, 8 Mar 2023 22:57:34 -0600 Message-Id: <20230309045738.1261000-1-honnappa.nagarahalli@arm.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 1) Patches 1/4, 2/4 - Few small corrections in mempool API documentation. 2) Patch 3/4 - The API for checking 'lcore ID is valid' is trivial, but it is the right thing to do. 3) Patch 4/4 - IMO, the 'lcore ID is valid' check is not necessary to be done during run time. If it is not valid, there is something seriously wrong in the system already or it is a programming error. Given that it is a data plane function, it makes sense to remove it from run time check. Honnappa Nagarahalli (4): mempool: clarify mempool cache flush API behavior mempool: clarify comments for mempool cache implementation eal: add API to check if lcore id is valid mempool: use lcore API to check if lcore ID is valid lib/eal/include/rte_lcore.h | 14 ++++++++++++++ lib/mempool/rte_mempool.c | 12 ++++++------ lib/mempool/rte_mempool.h | 13 ++++++++----- 3 files changed, 28 insertions(+), 11 deletions(-)