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 68D064897B; Sun, 19 Oct 2025 10:59:50 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3297A4278B; Sun, 19 Oct 2025 10:59:50 +0200 (CEST) Received: from fout-b7-smtp.messagingengine.com (fout-b7-smtp.messagingengine.com [202.12.124.150]) by mails.dpdk.org (Postfix) with ESMTP id CB9D34013F for ; Sun, 19 Oct 2025 10:59:48 +0200 (CEST) Received: from phl-compute-10.internal (phl-compute-10.internal [10.202.2.50]) by mailfout.stl.internal (Postfix) with ESMTP id B54191D000AC; Sun, 19 Oct 2025 04:59:47 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-10.internal (MEProxy); Sun, 19 Oct 2025 04:59:47 -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:subject:subject:to:to; s=fm2; t=1760864387; x=1760950787; bh=7VZLGNasCdIXcwbSMbPSWmIxt8EvzYmO9BM31B4b+ww=; b= iyvvATPmUS5t9h7YibW9n+7VL2Kor9awS8VyBZ04eL932aKF5IBXQ63EmDcoSiYf 1swqVjV0TmwWwUJhmPT0D8vDW8zjHtog+e8csFt8+h+0gF9oBIII61MEJNY6Y5jO zInYNx3gz6yo7iOOloyBLdSl+PHXpFs7atMPFEvWcuOXuZbmJw6KIGN/wYg7WDVj oMDmZ/4zrTdPKdKewLNI3UTijINHVGZSPLgMKhuTNIrzEJ+2y6XTWRLbQ7P39u/d xPGslUVMuuSzLYXyyDU3NthLAf+w0tRMtLyfvPMZsOkiU5NS60GAEh63BPPj/n6N Ff+ciYlfjxx2hotmtF3rfw== 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:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1760864387; x= 1760950787; bh=7VZLGNasCdIXcwbSMbPSWmIxt8EvzYmO9BM31B4b+ww=; b=l nJc4qEibNowQKV2dQ/+2IrTVM7tjaLfTkvxB80XB71lP3m0lnVAd90jkwwc9tjol cvfHykYPEVB4QT1T5IH0hgc4Jzeo3Rt9UjYDCWHXyxi/bt3QyAiHo4VFF8XdjRx8 njLMxyeS9eHls+lfSg4kXvmQTZXm3i2wjaEk5KBP9cMsf8P8YU3kUisAnplaPG/J cCCKn6a72goTMXcMlgMo4xp9CK2797mJPdRJksMXxU3Rea/PSphm1l9DfWUnS73X lHAoJIupaI/cjXGtilnOHxskjAKBWP/dXBufsnDaVFB4adZA7yUgsZAc5tmMXERC 9NubdVXkpelbUa/tYtHlw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggddufeeghedvucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhephffvvefufffkjghfggfgtgesthfuredttddtjeenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpeejudevheeiveduuddtveffgfdtgeekueevjeffjeegtdeggeekgfdv uefgfeekjeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtpdhnsggprhgtphhtthhopeejpdhm ohguvgepshhmthhpohhuthdprhgtphhtthhopehvrghtthhunhhurhhusehmrghrvhgvlh hlrdgtohhmpdhrtghpthhtohepuggvvhesughpughkrdhorhhgpdhrtghpthhtohepfhgv nhhgtghhvghnghifvghnsehhuhgrfigvihdrtghomhdprhgtphhtthhopegsrhhutggvrd hrihgthhgrrhgushhonhesihhnthgvlhdrtghomhdprhgtphhtthhopegrnhgrthholhih rdgsuhhrrghkohhvsehinhhtvghlrdgtohhmpdhrtghpthhtohepkhgvvhhinhdrlhgrrg htiiesihhnthgvlhdrtghomhdprhgtphhtthhopehjvghrihhnjhesmhgrrhhvvghllhdr tghomh X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 19 Oct 2025 04:59:45 -0400 (EDT) From: Thomas Monjalon To: Vamsi Krishna Attunuru Cc: "dev@dpdk.org" , "fengchengwen@huawei.com" , "bruce.richardson@intel.com" , "anatoly.burakov@intel.com" , "kevin.laatz@intel.com" , Jerin Jacob Subject: Re: [EXTERNAL] Re: [PATCH v4 1/1] lib/dma: add control-plane APIs for inter-domain DMA transfers Date: Sun, 19 Oct 2025 10:59:44 +0200 Message-ID: <4681397.3daJWjYHZt@thomas> In-Reply-To: References: <20251017122610.3126992-1-vattunuru@marvell.com> <3166338.vzjCzTo3RI@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 19/10/2025 10:37, Vamsi Krishna Attunuru: > >I'm not sure about having different API functions for leave and destroy. > >I think the last leaving should automatically call the destroy driver function. > > Thanks Thomas. The leave and destroy operations are invoked from different contexts. > Group joiners call leave to exit the group, whereas group creator calls destroy to > terminate the group after all members have left. I understand that, but why having a different function? You could destroy automatically when all have left.