DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vamsi Krishna Attunuru <vattunuru@marvell.com>
To: Vamsi Krishna Attunuru <vattunuru@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
	Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.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: [PATCH v0 1/1] doc: announce inter-device DMA capability support in dmadev
Date: Fri, 11 Jul 2025 15:05:00 +0000	[thread overview]
Message-ID: <SJ4PPFEA6F74CA26994FC5A642907B4680AA64BA@SJ4PPFEA6F74CA2.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250710085101.1678775-1-vattunuru@marvell.com>

Hi,

Gentle ping for reviews.

>-----Original Message-----
>From: Vamsi Krishna <vattunuru@marvell.com>
>Sent: Thursday, July 10, 2025 2:21 PM
>To: dev@dpdk.org; fengchengwen@huawei.com; Pavan Nikhilesh
>Bhagavatula <pbhagavatula@marvell.com>; kevin.laatz@intel.com;
>bruce.richardson@intel.com; mb@smartsharesystems.com
>Cc: Jerin Jacob <jerinj@marvell.com>; thomas@monjalon.net; Vamsi Krishna
>Attunuru <vattunuru@marvell.com>
>Subject: [PATCH v0 1/1] doc: announce inter-device DMA capability support in
>dmadev
>
>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>
>---
> 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.
>--
>2.34.1


      reply	other threads:[~2025-07-11 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-10  8:51 Vamsi Krishna
2025-07-11 15:05 ` 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=SJ4PPFEA6F74CA26994FC5A642907B4680AA64BA@SJ4PPFEA6F74CA2.namprd18.prod.outlook.com \
    --to=vattunuru@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=pbhagavatula@marvell.com \
    --cc=thomas@monjalon.net \
    /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).