DPDK patches and discussions
 help / color / mirror / Atom feed
From: Amit Prakash Shukla <amitprakashs@marvell.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Vamsi Krishna Attunuru <vattunuru@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Subject: RE: [PATCH v3 1/2] eventdev/dma: reorganize event DMA ops
Date: Thu, 16 May 2024 07:39:26 +0000	[thread overview]
Message-ID: <PH0PR18MB5167B829C6AACACEF881645CC8ED2@PH0PR18MB5167.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240417082645.4259-1-pbhagavatula@marvell.com>

> -----Original Message-----
> From: pbhagavatula@marvell.com <pbhagavatula@marvell.com>
> Sent: Wednesday, April 17, 2024 1:57 PM
> To: Jerin Jacob <jerinj@marvell.com>; Amit Prakash Shukla
> <amitprakashs@marvell.com>; Vamsi Krishna Attunuru
> <vattunuru@marvell.com>
> Cc: dev@dpdk.org; Pavan Nikhilesh Bhagavatula
> <pbhagavatula@marvell.com>
> Subject: [PATCH v3 1/2] eventdev/dma: reorganize event DMA ops
> 
> 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>
> ---
>  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           | 39 +++++++----------
>  lib/eventdev/rte_event_dma_adapter.c        | 27 ++++--------
>  lib/eventdev/rte_event_dma_adapter.h        | 46 +++++++++++++++------
>  6 files changed, 72 insertions(+), 88 deletions(-)
> 

Acked-by: Amit Prakash Shukla <amitprakashs@marvell.com>

  parent reply	other threads:[~2024-05-16  7:39 UTC|newest]

Thread overview: 13+ 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     ` Amit Prakash Shukla [this message]
2024-05-30 12:23       ` [PATCH v3 1/2] eventdev/dma: reorganize event DMA ops 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-05-16  7:36 ` [PATCH 1/2] eventdev/dma: reorganize event DMA ops 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=PH0PR18MB5167B829C6AACACEF881645CC8ED2@PH0PR18MB5167.namprd18.prod.outlook.com \
    --to=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).