From: Thomas Monjalon <thomas@monjalon.net>
To: Yaron Illouz <yaroni@radcom.com>
Cc: "users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
Radu Nicolau <radu.nicolau@intel.com>,
Akhil Goyal <gakhil@marvell.com>, Kai Ji <kai.ji@intel.com>,
Anoob Joseph <anoobj@marvell.com>
Subject: Re: ipsec on dpdk
Date: Wed, 31 Jul 2024 12:39:30 +0200 [thread overview]
Message-ID: <3105959.ktpJ11cQ8Q@thomas> (raw)
In-Reply-To: <AM9PR09MB49953F54F5C999BB0871C97CA1B62@AM9PR09MB4995.eurprd09.prod.outlook.com>
Hello,
Adding Cc some experts.
About the IPsec support, we are writing a document, it is in progress.
28/07/2024 14:51, Yaron Illouz:
> 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 ?
>
next prev parent reply other threads:[~2024-07-31 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 12:51 Yaron Illouz
2024-07-31 10:39 ` Thomas Monjalon [this message]
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=3105959.ktpJ11cQ8Q@thomas \
--to=thomas@monjalon.net \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=radu.nicolau@intel.com \
--cc=users@dpdk.org \
--cc=yaroni@radcom.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).