From: Thomas Monjalon <thomas@monjalon.net>
To: Vamsi Attunuru <vattunuru@marvell.com>
Cc: dev@dpdk.org, fengchengwen@huawei.com, pbhagavatula@marvell.com,
kevin.laatz@intel.com, bruce.richardson@intel.com,
mb@smartsharesystems.com, jerinj@marvell.com
Subject: Re: [PATCH v0 1/1] doc: announce inter-device DMA capability support in dmadev
Date: Mon, 21 Jul 2025 19:52:15 +0200 [thread overview]
Message-ID: <2992912.SvYEEZNnvj@thomas> (raw)
In-Reply-To: <20250710085101.1678775-1-vattunuru@marvell.com>
10/07/2025 10:51, Vamsi Krishna:
> From: Vamsi Attunuru <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>
> ---
> +* 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.
There are not enough acks (and all are from the same company).
Per our policy, it will miss the release 25.07.
You can probably do this change anyway,
and keep ABI compatibility by versioning the function.
prev parent reply other threads:[~2025-07-21 17:52 UTC|newest]
Thread overview: 14+ 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 ` [EXTERNAL] " Vamsi Krishna Attunuru
2025-07-15 0:59 ` fengchengwen
2025-07-15 5:35 ` [EXTERNAL] " Vamsi Krishna Attunuru
2025-07-16 4:14 ` fengchengwen
2025-07-16 10:59 ` Vamsi Krishna Attunuru
2025-07-17 1:40 ` fengchengwen
2025-07-18 2:29 ` Vamsi Krishna Attunuru
2025-07-21 17:52 ` Thomas Monjalon [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=2992912.SvYEEZNnvj@thomas \
--to=thomas@monjalon.net \
--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=pbhagavatula@marvell.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).