DPDK usage discussions
 help / color / mirror / Atom feed
From: Sana Kamboj <skamboj@qti.qualcomm.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: Steve Rizor <srizor@qti.qualcomm.com>,
	Saritha Goli <sgoli@qti.qualcomm.com>
Subject: Performance issue for Snow3G algorithm with DPDK 24.11 & IPSec 1.4
Date: Wed, 10 Sep 2025 20:00:17 +0000	[thread overview]
Message-ID: <BY5PR02MB67716FA66C0871DA9A77877E810EA@BY5PR02MB6771.namprd02.prod.outlook.com> (raw)

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

Hello,

We are using Intel IPSec multi-buffer library for our software security needs for Snow3G, AES and ZUC algorithms.
Are there any known issues or recommendations for Snow3G algorithm with DPDK 24.11 and IPSec version 1.4?

We recently switched to using DPDK 24.11 with IPSec version 1.4 from DPDK 22.11 with IPSec version 1.2.
The AES and ZUC performance look good with the upgrade, but the Snow3G performance has degraded within our application.
We have been using AES-NI Multi Buffer Crypto Poll Mode Driver for all algorithms as the DPDK documentation recommends this for better performance and algorithm mixing.

When we tried SNOW3G Crypto Poll Mode Driver for Snow3G with DPDK 24.11 and IPSec version 1.4, it is somehow performing better than AES-NI Multi Buffer Crypto Poll Mode Driver.

FYI, the standalone application results utilizing dpdk-test-crypto-perf tool still look good for all algorithms on both IPSec versions.

Could you please help us figure out the could for the performance degradation with Snow3G on our internal application?

Thanks,
Sana


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

                 reply	other threads:[~2025-09-10 20:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=BY5PR02MB67716FA66C0871DA9A77877E810EA@BY5PR02MB6771.namprd02.prod.outlook.com \
    --to=skamboj@qti.qualcomm.com \
    --cc=sgoli@qti.qualcomm.com \
    --cc=srizor@qti.qualcomm.com \
    --cc=users@dpdk.org \
    /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).