From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id DF5C742C4C; Wed, 7 Jun 2023 11:35:26 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B926940A84; Wed, 7 Jun 2023 11:35:26 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id 9A6C640698 for ; Wed, 7 Jun 2023 11:35:24 +0200 (CEST) Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 109055C0152; Wed, 7 Jun 2023 05:35:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 07 Jun 2023 05:35:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1686130524; x=1686216924; bh=OA3S+YkB42qBjzRj5HG+4C2/GQYDc3o+H2H UvIPDo/4=; b=LWHEXnFS7/6DFHzlyvSrDaG9X+raKbEiOMzTABmt17VKESDfjoT lP0uQhQlLIqzlAGPIfN1VuBb++WpjBst93Hb+rBZ1kPO5bNWOK2ZlSsca1UkHhKh Z55NIUIdOnoaLE9vsA2IRqp+bIBdSR/PrOlW2BwnnIcU9P+B/lUUg98UEXWQs79M nAqHLgNBrfusVUDD2trOWwIVqAs76e6zWagvDrP3wlkk7BMlTUj4bOX68AtS9CYt 8qtJzc3eBtycrWYtqT8wQQZQ5z/ohuMv8wOuVspYTkC3/x5SB8/7Te5hW5JjgwN5 RSen2W8dtL2IE2iZMifrbcQeEB9IEguBhww== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1686130524; x=1686216924; bh=OA3S+YkB42qBjzRj5HG+4C2/GQYDc3o+H2H UvIPDo/4=; b=WfiXZkwThKnqtwGbdMBwZnm+2tdce8Sm0pM9LdkVgG/L+YRuW9j /UH3e+PeO6dSJZVurKY6eYTtcxr9Eh8eWqyzbdVKAglt6fXVoRIIyoF0p+Bz+Hzl +1ckDcvWxhYxmGtYc6bT+WXN4tZzqbhMI+OIaC3ySG+2iaSB0GkkaCZhN0dmrNvQ VTJ9DRLqK9RngWLp9BWIYnGQPWJ7ioBe0f06suEvGjmb14hC1a9PjRE9ZsSFj6V0 7dFPVl9c98Egiv+fXuL2uwEgl1CmappDqlKDDj+DgHMRw67z1mUxqaOUV0/cQnp2 Qxlv+sFWkxNcqzOA16zXs1FDfHyoX72996w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgedtgedgudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfevufffkfgjfhgggfgtsehtuf ertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghs sehmohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnheptdejieeifeehtdffgf dvleetueeffeehueejgfeuteeftddtieekgfekudehtdfgnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonh drnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 7 Jun 2023 05:35:21 -0400 (EDT) From: Thomas Monjalon To: mb@smartsharesystems.com, olivier.matz@6wind.com, konstantin.v.ananyev@yandex.ru, honnappa.nagarahalli@arm.com Cc: dev@dpdk.org, ruifeng.wang@arm.com, kamalakshitha.aligeri@arm.com, wathsala.vithanage@arm.com, nd@arm.com Subject: Re: [PATCH 0/4] Small corrections in mempool Date: Wed, 07 Jun 2023 11:35:20 +0200 Message-ID: <84309111.BzKH3j3Lxt@thomas> In-Reply-To: <20230309045738.1261000-1-honnappa.nagarahalli@arm.com> References: <20230309045738.1261000-1-honnappa.nagarahalli@arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 Any update about this series? 09/03/2023 05:57, Honnappa Nagarahalli: > 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(-)