From: Thomas Monjalon <thomas@monjalon.net>
To: Vamsi Krishna Attunuru <vattunuru@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>,
"kevin.laatz@intel.com" <kevin.laatz@intel.com>,
Jerin Jacob <jerinj@marvell.com>
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 [thread overview]
Message-ID: <4681397.3daJWjYHZt@thomas> (raw)
In-Reply-To: <SJ4PPFEA6F74CA2C8C8EAE365AE5505773DA6F4A@SJ4PPFEA6F74CA2.namprd18.prod.outlook.com>
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.
next prev parent reply other threads:[~2025-10-19 8:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 12:33 [RFC] lib/dma: introduce inter-process and inter-OS DMA Vamsi Krishna
2025-09-18 11:06 ` Vamsi Krishna Attunuru
2025-09-19 9:02 ` fengchengwen
2025-09-22 11:48 ` [EXTERNAL] " Vamsi Krishna Attunuru
2025-09-24 4:14 ` Vamsi Krishna Attunuru
2025-09-25 1:34 ` fengchengwen
2025-10-01 5:57 ` Jerin Jacob
2025-10-06 13:59 ` Vamsi Krishna Attunuru
2025-10-09 2:27 ` Vamsi Krishna Attunuru
2025-10-09 11:08 ` fengchengwen
2025-10-10 10:40 ` Jerin Jacob
2025-09-25 2:06 ` fengchengwen
2025-10-10 14:46 ` [PATCH v2 1/1] " Vamsi Krishna
2025-10-12 1:49 ` fengchengwen
2025-10-13 4:07 ` [EXTERNAL] " Vamsi Krishna Attunuru
2025-10-13 18:10 ` [PATCH v2 1/1] lib/dma: add control-plane APIs for inter-domain DMA transfers Vamsi Krishna
2025-10-15 6:59 ` fengchengwen
2025-10-17 6:30 ` [EXTERNAL] " Vamsi Krishna Attunuru
2025-10-17 12:26 ` [PATCH v3 " Vamsi Krishna
2025-10-17 13:10 ` fengchengwen
2025-10-17 14:06 ` [PATCH v4 " Vamsi Krishna
2025-10-18 16:50 ` Thomas Monjalon
2025-10-19 8:12 ` Thomas Monjalon
2025-10-19 8:37 ` [EXTERNAL] " Vamsi Krishna Attunuru
2025-10-19 8:59 ` Thomas Monjalon [this message]
2025-10-19 9:40 ` Vamsi Krishna Attunuru
2025-10-19 10:05 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4681397.3daJWjYHZt@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=jerinj@marvell.com \
--cc=kevin.laatz@intel.com \
--cc=vattunuru@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).