DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Amit Prakash Shukla <amitprakashs@marvell.com>
Cc: Chengwen Feng <fengchengwen@huawei.com>,
	Kevin Laatz <kevin.laatz@intel.com>, <dev@dpdk.org>,
	<jerinj@marvell.com>, <mb@smartsharesystems.com>,
	<conor.walsh@intel.com>, <vattunuru@marvell.com>,
	 <g.singh@nxp.com>, <sachin.saxena@oss.nxp.com>,
	<hemant.agrawal@nxp.com>, <cheng1.jiang@intel.com>,
	<ndabilpuram@marvell.com>, <anoobj@marvell.com>
Subject: Re: [PATCH v1 1/2] dmadev: add DMA operation structure
Date: Mon, 18 Sep 2023 13:59:47 +0100	[thread overview]
Message-ID: <ZQhJw3SQmLelJFAr@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20230918123227.1562074-1-amitprakashs@marvell.com>

On Mon, Sep 18, 2023 at 06:02:26PM +0530, Amit Prakash Shukla wrote:
> For the event based DMA transfer, all the required parameters are to
> be sent as part of a structure. This patch adds a structure
> containing the parameters for event based DMA operation.
> 
> Signed-off-by: Amit Prakash Shukla <amitprakashs@marvell.com>
> ---
>  lib/dmadev/rte_dmadev.h | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/lib/dmadev/rte_dmadev.h b/lib/dmadev/rte_dmadev.h
> index b157ab7600..bf8db2d28d 100644
> --- a/lib/dmadev/rte_dmadev.h
> +++ b/lib/dmadev/rte_dmadev.h
> @@ -794,6 +794,18 @@ struct rte_dma_sge {
>  	uint32_t length; /**< The DMA operation length. */
>  };
>  
> +/**
> + * A structure used to hold event based DMA operation request entry.
> + */
> +struct rte_dma_op {

Would it be better called rte_dma_event_op, if it's just for use with
eventdev?

> +	struct rte_dma_sge *src_seg;      /**< Source segments. */
> +	struct rte_dma_sge *dst_seg;      /**< Destination segments. */
> +	uint16_t nb_src;                  /**< Number of source segments. */
> +	uint16_t nb_dst;                  /**< Number of destination segments. */
> +	uint64_t flags;                   /**< Flags related to the operation. */
> +	struct rte_mempool *op_mp;        /**< Mempool from which op is allocated. */
> +};
> +
>  #include "rte_dmadev_core.h"
>  
>  /**@{@name DMA operation flag
> -- 
> 2.25.1
> 

  parent reply	other threads:[~2023-09-18 13:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 12:32 Amit Prakash Shukla
2023-09-18 12:32 ` [PATCH v1 2/2] dmadev: get DMA device using device ID Amit Prakash Shukla
2023-09-18 13:42   ` Jerin Jacob
2023-09-18 13:47     ` [EXT] " Amit Prakash Shukla
2023-09-18 12:59 ` Bruce Richardson [this message]
2023-09-18 13:42   ` [EXT] Re: [PATCH v1 1/2] dmadev: add DMA operation structure Amit Prakash Shukla
2023-09-19 11:41 ` [PATCH v2] dmadev: get DMA device using device ID Amit Prakash Shukla
2023-09-21 15:43   ` Jerin Jacob
2023-09-26 11:09     ` [EXT] " 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=ZQhJw3SQmLelJFAr@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=amitprakashs@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=cheng1.jiang@intel.com \
    --cc=conor.walsh@intel.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=g.singh@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=kevin.laatz@intel.com \
    --cc=mb@smartsharesystems.com \
    --cc=ndabilpuram@marvell.com \
    --cc=sachin.saxena@oss.nxp.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).