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 DA80DA0C4C; Tue, 5 Oct 2021 18:39:11 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A0E74413E4; Tue, 5 Oct 2021 18:39:11 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id F243F413DD for ; Tue, 5 Oct 2021 18:39:09 +0200 (CEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id A2BC65C02AC; Tue, 5 Oct 2021 12:39:09 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 05 Oct 2021 12:39:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm2; bh= 0EanFQp0hMK0IBk8zmCGCxV6sGRZsNJBx8k4OvhwtbY=; b=nnqAt37qjTzy5T/0 lILg5/OgDfm86D1A7mxVLHjZtIZseIc0Od+dkvkZPharn/imvNC20kls2n2EBknz L+wUQPGsdpRtFpNZFLqTMXMmfrgbhm5LKfrYv1/ejc0VThVZ/az//+G4lhpqjpUE XpkXWF4vQbX4DupeoXp6NCXYhEiN2W/0yBDBB5ckEeQC/vIMPBPGrXQuBeZfyKQf vL+G18Lu8hKzMf68eUXkFn0nG6zaGygmL52K6DmI59UO0snQ3CFI8Fx5ggg6uqrW F7RQXge/Ra7sG1FMwezbC2Wg7JOZaLnyH3f4TnGz7J0hbAnfcf2MUwrld4uNNeJl q7UMGQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=0EanFQp0hMK0IBk8zmCGCxV6sGRZsNJBx8k4Ovhwt bY=; b=YxpShnFiLFFHd5WNrrULgLwI9N9j3vbEW1BkolqJTUGcaTH3J0kAEnlBb AKogQFKYSG4idqTYDAM0Hs8foU3n7IKKn7aQIn7YKxcd4/wtHrAKhHxVtnT/OMXT UaKxmRXsgGi8uKZo5WOVkJLA1LIz7BFZtXtnCJVopukedrlD7M5PFRNBPhqrb9RO ovZ14M23tlKBlng1Ev4DmQSngRw8jrRC/IXfj7ywKpxuF6gpTeQNDYX8Jr7Rpspp uPeYPMXAUpWfhzPixx9K/BeflbvWcl9of56VBMcf6VT3IwRHE+Yy6Vi1CfJmQPfR DzCHvbv97pTPF/TmAYv8d2lo8GzZg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudelgedguddtfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdej ueeiiedvffegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 5 Oct 2021 12:39:07 -0400 (EDT) From: Thomas Monjalon To: Dmitry Kozlyuk Cc: dev@dpdk.org, Matan Azrad , Olivier Matz , Andrew Rybchenko , mdr@ashroe.eu Date: Tue, 05 Oct 2021 18:39:05 +0200 Message-ID: <1672428.zglYOQ0Mhn@thomas> In-Reply-To: <20210929145249.2176811-3-dkozlyuk@nvidia.com> References: <20210818090755.2419483-1-dkozlyuk@nvidia.com> <20210929145249.2176811-1-dkozlyuk@nvidia.com> <20210929145249.2176811-3-dkozlyuk@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 2/4] mempool: add non-IO flag 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 Sender: "dev" 29/09/2021 16:52, dkozlyuk@oss.nvidia.com: > From: Dmitry Kozlyuk > > Mempool is a generic allocator that is not necessarily used for device > IO operations and its memory for DMA. Add MEMPOOL_F_NON_IO flag to mark > such mempools. > > Signed-off-by: Dmitry Kozlyuk > Acked-by: Matan Azrad > --- > doc/guides/rel_notes/release_21_11.rst | 3 +++ > lib/mempool/rte_mempool.h | 4 ++++ > 2 files changed, 7 insertions(+) > > diff --git a/doc/guides/rel_notes/release_21_11.rst b/doc/guides/rel_notes/release_21_11.rst > index f85dc99c8b..873beda633 100644 > --- a/doc/guides/rel_notes/release_21_11.rst > +++ b/doc/guides/rel_notes/release_21_11.rst > @@ -155,6 +155,9 @@ API Changes > +* mempool: Added ``MEMPOOL_F_NON_IO`` flag to give a hint to DPDK components > + that objects from this pool will not be used for device IO (e.g. DMA). This is not a breaking change, but I am OK to add this note. Any other opinion? > +#define MEMPOOL_F_NON_IO 0x0040 /**< Not used for device IO (DMA). */ > + * - MEMPOOL_F_NO_IO: If set, the mempool is considered to be > + * never used for device IO, i.e. DMA operations, > + * which may affect some PMD behavior. Not limited to PMD, it may affect some libs. I would reword the last line like this: "No impact on mempool behaviour, but it is a hint for other components."