From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Raghavendra Ningoji <raghavendra.ningoji@amd.com>, <dev@dpdk.org>,
"Thomas Monjalon" <thomas@monjalon.net>,
Bhagyada Modali <bhagyada.modali@amd.com>,
Robin Jarry <rjarry@redhat.com>, <Selwin.Sebastian@amd.com>,
Chengwen Feng <fengchengwen@huawei.com>
Subject: Re: [PATCH v2 1/3] dma/ae4dma: introduce AMD AE4DMA DMA PMD
Date: Mon, 22 Jun 2026 13:16:16 +0100 [thread overview]
Message-ID: <ajknkCqlD0N5arvf@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8w_67sp9iGW9+Gpwxx0ZkDYc4Zc2JKDtsPFFccU0UHePg@mail.gmail.com>
On Mon, Jun 22, 2026 at 02:06:55PM +0200, David Marchand wrote:
> On Mon, 25 May 2026 at 20:43, Raghavendra Ningoji
> <raghavendra.ningoji@amd.com> wrote:
> >
> > Add the skeleton of a new dmadev poll-mode driver for the AMD AE4DMA
> > hardware DMA engine, providing only PCI probe/remove and per-queue
> > hardware initialisation. An AE4DMA engine exposes 16 hardware command
> > queues, each with a 32-entry descriptor ring; the PMD maps each
> > hardware channel to its own dmadev with a single virtual channel,
> > so a PCI function appears as 16 dmadevs named "<pci-bdf>-ch0" ..
> > "<pci-bdf>-ch15".
>
> I am not familiar with DMA drivers, I am not sure it is something acceptable.
> @Chengwen for info.
>
This is similar with what is done by idxd driver when used as a PCI device
bound to vfio. We make the number of channels to configure a devarg, and
each channel becomes its own dmadev instance, since each channel is
independent from a user viewpoint. Only difference is that we use "q"
rather than "ch" in the naming. See [1] for what idxd does.
/Bruce
[1] https://github.com/DPDK/dpdk/blob/main/drivers/dma/idxd/idxd_pci.c#L326
next prev parent reply other threads:[~2026-06-22 12:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 18:18 [PATCH] dma/ae4dma: add AMD AE4DMA DMA PMD Raghavendra Ningoji
2026-05-21 14:28 ` David Marchand
2026-05-25 18:42 ` [PATCH v2 0/3] " Raghavendra Ningoji
2026-05-25 18:42 ` [PATCH v2 1/3] dma/ae4dma: introduce " Raghavendra Ningoji
2026-06-22 12:06 ` David Marchand
2026-06-22 12:16 ` Bruce Richardson [this message]
2026-06-24 0:38 ` fengchengwen
2026-06-25 18:41 ` Raghavendra Ningoji
2026-06-22 12:26 ` David Marchand
2026-06-22 12:37 ` Bruce Richardson
2026-06-25 18:43 ` Raghavendra Ningoji
2026-05-25 18:42 ` [PATCH v2 2/3] dma/ae4dma: add control path operations Raghavendra Ningoji
2026-06-22 12:15 ` David Marchand
2026-06-25 18:42 ` Raghavendra Ningoji
2026-05-25 18:42 ` [PATCH v2 3/3] dma/ae4dma: add data " Raghavendra Ningoji
2026-06-22 12:25 ` [PATCH v2 0/3] dma/ae4dma: add AMD AE4DMA DMA PMD David Marchand
2026-06-25 18:47 ` [PATCH v3 " Raghavendra Ningoji
2026-06-25 18:47 ` [PATCH v3 1/3] dma/ae4dma: introduce " Raghavendra Ningoji
2026-06-27 0:01 ` fengchengwen
2026-06-25 18:47 ` [PATCH v3 2/3] dma/ae4dma: add control path operations Raghavendra Ningoji
2026-06-27 0:09 ` fengchengwen
2026-06-25 18:47 ` [PATCH v3 3/3] dma/ae4dma: add data " Raghavendra Ningoji
2026-06-27 0:23 ` fengchengwen
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=ajknkCqlD0N5arvf@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=Selwin.Sebastian@amd.com \
--cc=bhagyada.modali@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=raghavendra.ningoji@amd.com \
--cc=rjarry@redhat.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