DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Vamsi Krishna <vattunuru@marvell.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com,
	anatoly.burakov@intel.com, kevin.laatz@intel.com,
	jerinj@marvell.com, stephen@networkplumber.org,
	fengchengwen <fengchengwen@huawei.com>
Subject: Re: [PATCH v4 1/1] lib/dma: introduce inter-process and inter-OS DMA
Date: Sat, 18 Oct 2025 17:55:09 +0200	[thread overview]
Message-ID: <5076338.MSiuQNM8U4@thomas> (raw)
In-Reply-To: <b0ba957e-c147-2a55-283b-281063235bba@huawei.com>

> > Modern DMA hardware supports data transfers between multiple DMA
> > devices, facilitating data communication across isolated domains,
> > containers, or operating systems. These DMA transfers function as
> > standard memory-to-memory operations, but with source or destination
> > addresses residing in different process or OS address space. The
> > exchange of these addresses between processes is handled through
> > private driver mechanism, which are beyond the scope of this
> > specification change.
> >
> > This commit introduces new capability flags to advertise driver support
> > for inter-process and inter-OS domain DMA transfers. It adds a mechanism
> > to specify source and destination handlers via the vchan configuration.
> > Until standardized control-plane APIs are defined for various categories
> > of DMA devices, these handler details can be exchanged through private
> > driver mechanisms.
> >
> > Signed-off-by: Vamsi Attunuru<vattunuru@marvell.com>
> Acked-by: Chengwen Feng <fengchengwen@huawei.com>

Added release notes and applied, thanks.




      parent reply	other threads:[~2025-10-18 15:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <--in-reply-to=20251010144631.713063-1-vattunuru@marvell.com>
2025-10-13  4:21 ` [PATCH v3 " Vamsi Krishna
2025-10-13  7:52   ` fengchengwen
2025-10-13 18:31     ` [EXTERNAL] " Vamsi Krishna Attunuru
2025-10-15  7:09       ` fengchengwen
2025-10-16 10:20         ` Vamsi Krishna Attunuru
2025-10-15 17:26   ` Stephen Hemminger
2025-10-16 10:15     ` [EXTERNAL] " Vamsi Krishna Attunuru
2025-10-15 17:27   ` Stephen Hemminger
2025-10-17  5:42   ` [PATCH v4 " Vamsi Krishna
2025-10-17 13:13     ` fengchengwen
2025-10-18 11:05       ` [EXTERNAL] " Vamsi Krishna Attunuru
2025-10-18 15:55       ` 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=5076338.MSiuQNM8U4@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=stephen@networkplumber.org \
    --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).