DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Amit Prakash Shukla <amitprakashs@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
	dev@dpdk.org, pbhagavatula@marvell.com,  vattunuru@marvell.com,
	ndabilpuram@marvell.com, anoobj@marvell.com,
	 asasidharan@marvell.com
Subject: Re: [PATCH v4] app/eventdev: support DMA adapter test
Date: Wed, 13 Mar 2024 18:48:30 +0530	[thread overview]
Message-ID: <CALBAE1Ozn0Et_-eG+kcHMOK-ncEWmksS8OraOT=EVRCaXNUKpg@mail.gmail.com> (raw)
In-Reply-To: <20240312143023.2651468-1-amitprakashs@marvell.com>

On Tue, Mar 12, 2024 at 8:10 PM Amit Prakash Shukla
<amitprakashs@marvell.com> wrote:
>
> Added performance test support for DMA adapter.
>
> Signed-off-by: Amit Prakash Shukla <amitprakashs@marvell.com>
> Acked-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
> v4:
> - Updated release notes.
>
> v3:
> - Resolved review comments.
>
> v2:
> - Fixed intel compilation error.


> +* **Added DMA producer mode in test-eventdev.**
> +
> +  * DMA producer mode helps to measure performance of OP_FORWARD mode of event DMA
> +    adapter.

Changed to following and  applied to dpdk-next-net-eventdev/for-main. Thanks

+* **Added DMA producer mode in test-eventdev.**
+
+  * Added DMA producer mode to measure performance of ``OP_FORWARD``
mode of event DMA
+    adapter.
+

> +
>

      reply	other threads:[~2024-03-13 13:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 13:26 [PATCH] " Amit Prakash Shukla
2024-02-28  6:01 ` [PATCH v2] " Amit Prakash Shukla
2024-03-01 12:57   ` Pavan Nikhilesh Bhagavatula
2024-03-01 14:42     ` Amit Prakash Shukla
2024-03-06 19:05   ` [PATCH v3] " Amit Prakash Shukla
2024-03-07  3:56     ` Pavan Nikhilesh Bhagavatula
2024-03-12 13:10       ` Jerin Jacob
2024-03-12 14:30     ` [PATCH v4] " Amit Prakash Shukla
2024-03-13 13:18       ` Jerin Jacob [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='CALBAE1Ozn0Et_-eG+kcHMOK-ncEWmksS8OraOT=EVRCaXNUKpg@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=amitprakashs@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=asasidharan@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@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).