From: Akhil Goyal <gakhil@marvell.com>
To: Suanming Mou <suanmingm@nvidia.com>,
"ciara.power@intel.com" <ciara.power@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXT] [PATCH 0/2] app/test-crypto-perf: fix multi-segment issue
Date: Thu, 29 Feb 2024 17:01:03 +0000 [thread overview]
Message-ID: <CO6PR18MB448473A223BC0836D552AB22D85F2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240103040024.720600-1-suanmingm@nvidia.com>
> This commit fixes the bugs in multi-segment size calculation.
>
> Suanming Mou (2):
> app/test-crypto-perf: fix copy segment size calculation
> app/test-crypto-perf: fix dst_mbuf size calculation
>
> app/test-crypto-perf/cperf_test_common.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
Series Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto
next prev parent reply other threads:[~2024-02-29 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 4:00 Suanming Mou
2024-01-03 4:00 ` [PATCH 1/2] app/test-crypto-perf: fix copy segment size calculation Suanming Mou
2024-02-01 13:16 ` Suanming Mou
2024-01-03 4:00 ` [PATCH 2/2] app/test-crypto-perf: fix dst_mbuf " Suanming Mou
2024-02-29 17:01 ` Akhil Goyal [this message]
2024-02-29 17:03 ` [EXT] [PATCH 0/2] app/test-crypto-perf: fix multi-segment issue Akhil Goyal
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=CO6PR18MB448473A223BC0836D552AB22D85F2@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=ciara.power@intel.com \
--cc=dev@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).