From: Yaron Illouz <yaroni@radcom.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: ipsec on dpdk
Date: Sun, 28 Jul 2024 12:51:06 +0000 [thread overview]
Message-ID: <AM9PR09MB49953F54F5C999BB0871C97CA1B62@AM9PR09MB4995.eurprd09.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
Hi
I am interested to do ipsec encoding and decoding in my dpdk application
From my readings, i understand ipsec can be done one time in the nic (inline ipsec) or with multiple calls (rte_cryptodev_enqueue_burst, rte_cryptodev_dequeue_burst....)
1. If ipsec is done by nic I only need to call rte_ipsec_pkt_process(...) without other functions?
I use rte_eth_rx_burst to read from nic.
1. Where do I see list of nic that support nic inline ipsec? I believe not all dpdk nic support it.
2. How much does it impact performance ? is there a table of performance per nic?
3. My application is multi process, I can see in documentation :
“Currently, the security library does not support the case of multi-process. It will be updated in the future releases.” From https://doc.dpdk.org/guides/prog_guide/rte_security.html
So ipsec also is not supported for multi process application?
Even if done inline by the nic?
And what about non inline ipsec for multi process applications?
1. Is ip sec also supported in multi queue with rte flow in the inline ipsec ?
[-- Attachment #2: Type: text/html, Size: 6285 bytes --]
next reply other threads:[~2024-07-28 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 12:51 Yaron Illouz [this message]
2024-07-31 10:39 ` Thomas Monjalon
2024-07-31 18:06 ` [EXTERNAL] " 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=AM9PR09MB49953F54F5C999BB0871C97CA1B62@AM9PR09MB4995.eurprd09.prod.outlook.com \
--to=yaroni@radcom.com \
--cc=dev@dpdk.org \
--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).