From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Anoob Joseph <anoobj@marvell.com>,
Vamsi Krishna Attunuru <vattunuru@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
"kevin.laatz@intel.com" <kevin.laatz@intel.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"mb@smartsharesystems.com" <mb@smartsharesystems.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [EXTERNAL] [PATCH v0 1/1] doc: announce inter-device DMA capability support in dmadev
Date: Mon, 14 Jul 2025 05:30:37 +0000 [thread overview]
Message-ID: <PH0PR18MB4086496D9FFDFF62A20C4B03DE54A@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
In-Reply-To: <PH0PR18MB467232EDCA9A5B6BFB829585DF54A@PH0PR18MB4672.namprd18.prod.outlook.com>
>> From: Vamsi Attunuru <mailto:vattunuru@marvell.com>
>>
>> Modern DMA hardware supports data transfer between multiple
>> DMA devices, enabling data communication across isolated domains or
>> containers. To facilitate this, the ``dmadev`` library requires changes
>> to allow devices to register with or unregisters from DMA groups for
>> inter-device communication. This feature is planned for inclusion
>> in DPDK 25.11.
>>
>> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
>
>Acked-by: Anoob Joseph <anoobj@marvell.com>
Acked-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
>
>
next prev parent reply other threads:[~2025-07-14 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 8:51 Vamsi Krishna
2025-07-11 15:05 ` Vamsi Krishna Attunuru
2025-07-14 10:32 ` Vamsi Krishna Attunuru
2025-07-14 5:24 ` [EXTERNAL] " Anoob Joseph
2025-07-14 5:30 ` Pavan Nikhilesh Bhagavatula [this message]
2025-07-14 10:17 ` Medvedkin, Vladimir
2025-07-14 10:53 ` [EXTERNAL] " Vamsi Krishna Attunuru
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=PH0PR18MB4086496D9FFDFF62A20C4B03DE54A@PH0PR18MB4086.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--cc=anoobj@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=jerinj@marvell.com \
--cc=kevin.laatz@intel.com \
--cc=mb@smartsharesystems.com \
--cc=thomas@monjalon.net \
--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).