DPDK patches and discussions
 help / color / mirror / Atom feed
From: Amit Prakash Shukla <amitprakashs@marvell.com>
To: Shiva Shankar Kommula <kshankar@marvell.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Vamsi Krishna Attunuru <vattunuru@marvell.com>,
	"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
	Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Subject: RE: [PATCH RFC 3/4] doc: update prog guide to use rte_dma_op
Date: Tue, 25 Feb 2025 14:13:53 +0000	[thread overview]
Message-ID: <PH0PR18MB5167AFAA73349A4E69B98552C8C32@PH0PR18MB5167.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250129143649.3887989-3-kshankar@marvell.com>



> -----Original Message-----
> From: Kommula Shiva Shankar <kshankar@marvell.com>
> Sent: Wednesday, January 29, 2025 8:07 PM
> To: Jerin Jacob <jerinj@marvell.com>; Amit Prakash Shukla
> <amitprakashs@marvell.com>; Vamsi Krishna Attunuru
> <vattunuru@marvell.com>; fengchengwen@huawei.com; dev@dpdk.org
> Cc: Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>; Pavan Nikhilesh
> Bhagavatula <pbhagavatula@marvell.com>
> Subject: [PATCH RFC 3/4] doc: update prog guide to use rte_dma_op
> 
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
> 
> Update the documentation to replace all instances of
> rte_event_dma_adapter_op with rte_dma_op
> 
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> Change-Id: I0fe65d18f4601709826c11c6738cacec8991515d
> ---
>  doc/guides/prog_guide/eventdev/event_dma_adapter.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 

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


> diff --git a/doc/guides/prog_guide/eventdev/event_dma_adapter.rst
> b/doc/guides/prog_guide/eventdev/event_dma_adapter.rst
> index e040d89e8b..e8437a3297 100644
> --- a/doc/guides/prog_guide/eventdev/event_dma_adapter.rst
> +++ b/doc/guides/prog_guide/eventdev/event_dma_adapter.rst
> @@ -144,7 +144,7 @@ on which it enqueues events towards the DMA
> adapter using ``rte_event_enqueue_bu
>     uint32_t cap;
>     int ret;
> 
> -   /* Fill in event info and update event_ptr with rte_event_dma_adapter_op
> */
> +   /* Fill in event info and update event_ptr with rte_dma_op */
>     memset(&ev, 0, sizeof(ev));
>     .
>     .
> @@ -244,11 +244,11 @@ Set event response information
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
>  In the ``RTE_EVENT_DMA_ADAPTER_OP_FORWARD`` /
> ``RTE_EVENT_DMA_ADAPTER_OP_NEW`` mode, -the application specifies the
> dmadev ID and vchan ID in ``struct rte_event_dma_adapter_op``
> +the application specifies the dmadev ID and vchan ID in ``struct
> +rte_dma_op``
>  and the event information (response information)  needed to enqueue an
> event after the DMA operation has completed.
>  The response information is specified in ``struct rte_event`` -and appended
> to the ``struct rte_event_dma_adapter_op``.
> +and appended to the ``struct rte_dma_op``.
> 
> 
>  Start the adapter instance
> --
> 2.43.0


  reply	other threads:[~2025-02-25 14:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 14:36 [PATCH RFC 1/4] dmadev: add enqueue dequeue operations Kommula Shiva Shankar
2025-01-29 14:36 ` [PATCH RFC 2/4] eventdev: refactor rte_event_dma_adapater_op calls Kommula Shiva Shankar
2025-02-25 14:11   ` Amit Prakash Shukla
2025-01-29 14:36 ` [PATCH RFC 3/4] doc: update prog guide to use rte_dma_op Kommula Shiva Shankar
2025-02-25 14:13   ` Amit Prakash Shukla [this message]
2025-01-29 14:36 ` [PATCH RFC 4/4] dma/cnxk: implement enqueue dequeue ops Kommula Shiva Shankar

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=PH0PR18MB5167AFAA73349A4E69B98552C8C32@PH0PR18MB5167.namprd18.prod.outlook.com \
    --to=amitprakashs@marvell.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=jerinj@marvell.com \
    --cc=kshankar@marvell.com \
    --cc=ndabilpuram@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).