DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Suanming Mou <suanmingm@nvidia.com>,
	Anoob Joseph <anoobj@marvell.com>,
	"ciara.power@intel.com" <ciara.power@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXT] [PATCH v2] app/test-crypto-perf: add missed resubmission fix
Date: Thu, 29 Feb 2024 17:03:01 +0000	[thread overview]
Message-ID: <CO6PR18MB448411A6D870962A9788D99AD85F2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240115080830.1051786-1-suanmingm@nvidia.com>

> Currently, after enqueue_burst, there may be ops_unused ops
> left for next round enqueue. And in next round preparation,
> only ops_needed ops will be added. But if in the final round
> the left ops is less than ops_needed, there will be invalid
> ops between the new needed ops and previous unused ops. The
> previous unused ops should be moved front after the needed
> ops.
> 
> In the commit[1], an resubmission fix was added to throughput
> test, and the fix was missed for verify.
> 
> This commit adds the missed resubmission fix for verify.
> 
> [1]
> commit 44e2980b70d1 ("app/crypto-perf: fix crypto operation resubmission")
> 
> Fixes: f8be1786b1b8 ("app/crypto-perf: introduce performance test application")
> 
> Cc: stable@dpdk.org
> 
> Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
> 
> Acked-by: Anoob Joseph <anoobj@marvell.com>
> ---
> 
> v2: code-style update.
> 
Applied to dpdk-next-crypto
Thanks.

      reply	other threads:[~2024-02-29 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05  6:55 [PATCH] " Suanming Mou
2024-01-10 14:46 ` [EXT] " Anoob Joseph
2024-01-15  7:46   ` Suanming Mou
2024-01-15  8:08 ` [PATCH v2] " Suanming Mou
2024-02-29 17:03   ` Akhil Goyal [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=CO6PR18MB448411A6D870962A9788D99AD85F2@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=suanmingm@nvidia.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).