From: Vamsi Krishna Attunuru <vattunuru@marvell.com>
To: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: RE: [EXTERNAL] Re: [PATCH v0 1/1] doc: announce inter-device DMA capability support in dmadev
Date: Mon, 14 Jul 2025 10:53:37 +0000 [thread overview]
Message-ID: <SJ4PPFEA6F74CA26815C0A378DC578B0AE7A654A@SJ4PPFEA6F74CA2.namprd18.prod.outlook.com> (raw)
In-Reply-To: <8d868117-56e0-4acd-991c-504a5dc451d5@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3146 bytes --]
Hi Vladimir,
Currently, mem-to-mem dma transfers happen within a single process address space. This feature aims to extend support for transfers across multiple process address spaces to meet the requirements of inter-process or inter-VM networking. In environments where share memory is not feasible due to security concerns, this feature allows controlled software to use DMA for packet transfers as needed.
Regards.
From: Medvedkin, Vladimir <vladimir.medvedkin@intel.com>
Sent: Monday, July 14, 2025 3:47 PM
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [EXTERNAL] Re: [PATCH v0 1/1] doc: announce inter-device DMA capability support in dmadev
Hi Vamsi, Could you please tell us more about usecases for this feature? Thanks! On 7/10/2025 9: 51 AM, Vamsi Krishna wrote: > From: Vamsi Attunuru <vattunuru@ marvell. com> > > Modern DMA hardware supports data transfer between
ZjQcmQRYFpfptBannerStart
Prioritize security for external emails:
Confirm sender and content safety before clicking links or opening attachments
Report Suspicious <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/CRVmXkqW!ti3Yn35UY3X61OwcGRf6bRAsmnzalHb1b3IuGKm4KAmFKsaahO5TQ00KAcbC6zX9rZkmmbglmeBA6oy8diWgp0Bz2fptvfWCiA$>
ZjQcmQRYFpfptBannerEnd
Hi Vamsi,
Could you please tell us more about usecases for this feature?
Thanks!
On 7/10/2025 9:51 AM, Vamsi Krishna wrote:
> From: Vamsi Attunuru <vattunuru@marvell.com<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<mailto:vattunuru@marvell.com>>
> ---
> doc/guides/rel_notes/deprecation.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index e2d4125308..46836244dd 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -152,3 +152,10 @@ Deprecation Notices
> * bus/vmbus: Starting DPDK 25.11, all the vmbus API defined in
> ``drivers/bus/vmbus/rte_bus_vmbus.h`` will become internal to DPDK.
> Those API functions are used internally by DPDK core and netvsc PMD.
> +
> +* dmadev: a new capability flag ``RTE_DMA_CAPA_INTER_DEV`` will be added
> + to advertise DMA device's inter-device DMA copy capability. To enable
> + this functionality, a few dmadev APIs will be added to configure the DMA
> + access groups, facilitating coordinated data communication between devices.
> + A new ``dev_idx`` field will be added to the ``struct rte_dma_vchan_conf``
> + structure to configure a vchan for data transfers between any two DMA devices.
--
Regards,
Vladimir
[-- Attachment #2: Type: text/html, Size: 12230 bytes --]
prev parent reply other threads:[~2025-07-14 10:53 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
2025-07-14 10:17 ` Medvedkin, Vladimir
2025-07-14 10:53 ` Vamsi Krishna Attunuru [this message]
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=SJ4PPFEA6F74CA26815C0A378DC578B0AE7A654A@SJ4PPFEA6F74CA2.namprd18.prod.outlook.com \
--to=vattunuru@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=vladimir.medvedkin@intel.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).