From: Bruce Richardson <bruce.richardson@intel.com>
To: <pbhagavatula@marvell.com>
Cc: <jerinj@marvell.com>, <vattunuru@marvell.com>, <g.singh@nxp.com>,
<sachin.saxena@nxp.com>, <hemant.agrawal@nxp.com>,
<fengchengwen@huawei.com>, <kevin.laatz@intel.com>,
<conor.walsh@intel.com>, <gmuthukrishn@marvell.com>,
<vvelumuri@marvell.com>, <anatoly.burakov@intel.com>,
<dev@dpdk.org>
Subject: Re: [25.11 PATCH v3 0/5] Introduce DMA enqueue/dequeue operations
Date: Mon, 26 May 2025 09:15:09 +0100 [thread overview]
Message-ID: <aDQjDZowik8E7Jfh@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250524091316.10056-1-pbhagavatula@marvell.com>
On Sat, May 24, 2025 at 02:43:10PM +0530, pbhagavatula@marvell.com wrote:
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Introduce DMA enqueue/dequeue operations to the DMA device library.
>
> Add configuration flags to rte_dma_config instead of boolean for
> individual features.
>
> The enqueue/dequeue operations allow applications to communicate with the
> DMA device using the rte_dma_op structure, providing a more flexible and
> efficient way to manage DMA operations.
>
While I have no really strong objections to this addition to the dmadev
API, I'd appreciate if you could explain WHY or how this method of working
is more efficient in your usecase? When designing the dmadev APIs
originally, we looked at using both an enqueue-type API as well as the
implemented individual-op-based APIs. IIRC at that time testing showed that
using the single ops directly was faster than using the enqueue APIs, so
I'm wondering what exactly has changed, or is different about your usecase?
/Bruce
prev parent reply other threads:[~2025-05-26 8:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 10:09 [25.11 PATCH 0/3] " pbhagavatula
2025-04-16 10:09 ` [25.11 PATCH 1/3] dmadev: add enqueue dequeue operations pbhagavatula
2025-04-24 7:01 ` fengchengwen
2025-05-02 10:38 ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2025-04-16 10:09 ` [25.11 PATCH 2/3] dma/cnxk: implement enqueue dequeue ops pbhagavatula
2025-04-16 10:09 ` [25.11 PATCH 3/3] eventdev: refactor DMA adapter ops pbhagavatula
2025-05-19 18:55 ` [25.11 PATCH v2 0/5] Introduce DMA enqueue/dequeue operations pbhagavatula
2025-05-19 18:56 ` [25.11 PATCH v2 1/5] dmadev: add enqueue dequeue operations pbhagavatula
2025-05-19 18:56 ` [25.11 PATCH v2 2/5] test/dma: " pbhagavatula
2025-05-19 18:56 ` [25.11 PATCH v2 3/5] app/dma-perf: add option to measure enq deq ops pbhagavatula
2025-05-19 18:56 ` [25.11 PATCH v2 4/5] dma/cnxk: implement enqueue dequeue ops pbhagavatula
2025-05-19 18:56 ` [25.11 PATCH v2 5/5] eventdev: refactor DMA adapter ops pbhagavatula
2025-05-24 9:13 ` [25.11 PATCH v3 0/5] Introduce DMA enqueue/dequeue operations pbhagavatula
2025-05-24 9:13 ` [25.11 PATCH v3 1/5] dmadev: add enqueue dequeue operations pbhagavatula
2025-05-24 9:13 ` [25.11 PATCH v3 2/5] test/dma: " pbhagavatula
2025-05-24 9:13 ` [25.11 PATCH v3 3/5] app/dma-perf: add option to measure enq deq ops pbhagavatula
2025-05-24 9:13 ` [25.11 PATCH v3 4/5] dma/cnxk: implement enqueue dequeue ops pbhagavatula
2025-05-24 9:13 ` [25.11 PATCH v3 5/5] eventdev: refactor DMA adapter ops pbhagavatula
2025-05-26 8:15 ` Bruce Richardson [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=aDQjDZowik8E7Jfh@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=conor.walsh@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=g.singh@nxp.com \
--cc=gmuthukrishn@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=kevin.laatz@intel.com \
--cc=pbhagavatula@marvell.com \
--cc=sachin.saxena@nxp.com \
--cc=vattunuru@marvell.com \
--cc=vvelumuri@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).