DPDK patches and discussions
 help / color / mirror / Atom feed
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: crypto decryption support in test-crypto-perf pmd-cycle-count test
Date: Fri, 21 Jul 2023 11:48:40 +0000	[thread overview]
Message-ID: <CO6PR18MB44846D0715B1B446EC15EE6ED83FA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CO6PR12MB5396A68990DBB370789CD8E0C13FA@CO6PR12MB5396.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

Hi Suanming,

The pmd-cycle-count mode is for counting the cycles for enqueue and dequeue.
It does not matter what is the content of the packet, as we are not validating the content
after dequeue of the packet. PMD/Hw will assume it as plain/encrypted payload and
will process it as per the session attached.
Hence, doing memcpy to mbuf is not required.

Regards,
Akhil

From: Suanming Mou <suanmingm@nvidia.com>
Sent: Friday, July 21, 2023 4:06 PM
To: ciara.power@intel.com; Akhil Goyal <gakhil@marvell.com>
Cc: dev@dpdk.org
Subject: [EXT] crypto decryption support in test-crypto-perf pmd-cycle-count test

External Email
________________________________
Hi Guys,

Sorry for the inconvenience.
I have one small question with pmd-cycle-count test in test-crypto-perf application.
As in pmd-cycle-count run code, I don't see the cperf_mbuf_set() function is called to fill the test data.
So for decryption, I assume it will always fails. Feel like pmd-cycle-count test does not expect to support decryption. Or is it a bug?

I have no idea with the application design background, is it expected?

Thanks,
Suanming Mou

[-- Attachment #2: Type: text/html, Size: 4282 bytes --]

  reply	other threads:[~2023-07-21 11:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 10:36 Suanming Mou
2023-07-21 11:48 ` Akhil Goyal [this message]
2023-07-21 11:52   ` Suanming Mou
2023-07-21 12:03     ` Akhil Goyal
2023-07-21 12:09       ` Suanming Mou

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=CO6PR18MB44846D0715B1B446EC15EE6ED83FA@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).