From: Jerin Jacob <jerinjacobk@gmail.com>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com,
Amit Prakash Shukla <amitprakashs@marvell.com>,
Vamsi Attunuru <vattunuru@marvell.com>,
dev@dpdk.org
Subject: Re: [PATCH v4 1/2] eventdev/dma: reorganize event DMA ops
Date: Fri, 7 Jun 2024 15:50:52 +0530 [thread overview]
Message-ID: <CALBAE1NGh=d0Q-R4DyX93CnWROX562Z4bQkNSBaYGjyxPuNTcg@mail.gmail.com> (raw)
In-Reply-To: <20240530124437.1870-1-pbhagavatula@marvell.com>
On Thu, May 30, 2024 at 6:14 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Re-organize event DMA ops structure to allow holding
> source and destination pointers without the need for
> additional memory, the mempool allocating memory for
> rte_event_dma_adapter_ops can size the structure to
> accommodate all the needed source and destination
> pointers.
>
> Add multiple words for holding user metadata, adapter
> implementation specific metadata and event metadata.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> Acked-by: Amit Prakash Shukla <amitprakashs@marvell.com>
> ---
> v4 Changes:
> - Reduce unreleated driver changes and move to 2/2.
> v3 Changes:
> - Fix stdatomic compilation.
> v2 Changes:
> - Fix 32bit compilation
>
> app/test-eventdev/test_perf_common.c | 26 ++++--------
> app/test/test_event_dma_adapter.c | 20 +++------
> doc/guides/prog_guide/event_dma_adapter.rst | 2 +-
> drivers/dma/cnxk/cnxk_dmadev_fp.c | 20 ++++-----
> lib/eventdev/rte_event_dma_adapter.c | 27 ++++--------
> lib/eventdev/rte_event_dma_adapter.h | 46 +++++++++++++++------
> 6 files changed, 66 insertions(+), 75 deletions(-)
> * instance.
> */
> struct rte_event_dma_adapter_op {
> - struct rte_dma_sge *src_seg;
Even though it is experimental , Changes in public structure need to
updated in release notes.
Please send the next version.
next prev parent reply other threads:[~2024-06-07 10:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-06 10:13 [PATCH " pbhagavatula
2024-04-06 10:13 ` [PATCH 2/2] dma/cnxk: remove completion pool pbhagavatula
2024-04-16 8:56 ` Vamsi Krishna Attunuru
2024-04-17 5:58 ` [PATCH v2 1/2] eventdev/dma: reorganize event DMA ops pbhagavatula
2024-04-17 5:58 ` [PATCH v2 2/2] dma/cnxk: remove completion pool pbhagavatula
2024-04-17 8:26 ` [PATCH v3 1/2] eventdev/dma: reorganize event DMA ops pbhagavatula
2024-04-17 8:26 ` [PATCH v3 2/2] dma/cnxk: remove completion pool pbhagavatula
2024-05-16 7:39 ` [PATCH v3 1/2] eventdev/dma: reorganize event DMA ops Amit Prakash Shukla
2024-05-30 12:23 ` Jerin Jacob
2024-05-30 17:35 ` [EXTERNAL] " Pavan Nikhilesh Bhagavatula
2024-05-30 12:44 ` [PATCH v4 " pbhagavatula
2024-05-30 12:44 ` [PATCH v4 2/2] dma/cnxk: remove completion pool pbhagavatula
2024-06-07 10:20 ` Jerin Jacob [this message]
2024-06-07 10:36 ` [PATCH v5 1/2] eventdev/dma: reorganize event DMA ops pbhagavatula
2024-06-07 10:36 ` [PATCH v5 2/2] dma/cnxk: remove completion pool pbhagavatula
2024-06-08 6:16 ` [PATCH v5 1/2] eventdev/dma: reorganize event DMA ops Jerin Jacob
2024-05-16 7:36 ` [PATCH " Amit Prakash Shukla
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='CALBAE1NGh=d0Q-R4DyX93CnWROX562Z4bQkNSBaYGjyxPuNTcg@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=amitprakashs@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.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).