From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v3] examples/ipsec-secgw: remove limitation for crypto sessions
Date: Thu, 23 Apr 2020 00:12:51 +0000 [thread overview]
Message-ID: <BYAPR11MB3301C2EC1D564D021C7A5E279AD30@BYAPR11MB3301.namprd11.prod.outlook.com> (raw)
In-Reply-To: <134a692052e2017bcb0312b3d572e68cd2f7d1e9.1587410155.git.vladimir.medvedkin@intel.com>
>
> Get rid of hardcoded limit of cryptodev sessions.
>
> Fixes: e1143d7dbbf4 ("examples/ipsec-secgw: get rid of maximum SA limitation")
> Cc: vladimir.medvedkin@intel.com
>
> Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> ---
> examples/ipsec-secgw/ipsec-secgw.c | 25 +++++++++++++++++++------
> examples/ipsec-secgw/ipsec.h | 3 +++
> examples/ipsec-secgw/sa.c | 9 +++++++++
> 3 files changed, 31 insertions(+), 6 deletions(-)
>
> diff --git a/examples/ipsec-secgw/ipsec-secgw.c b/examples/ipsec-secgw/ipsec-secgw.c
> index 5fde4f7..30fc985 100644
> --- a/examples/ipsec-secgw/ipsec-secgw.c
> +++ b/examples/ipsec-secgw/ipsec-secgw.c
> @@ -62,7 +62,6 @@ volatile bool force_quit;
>
> #define CDEV_QUEUE_DESC 2048
> #define CDEV_MAP_ENTRIES 16384
> -#define CDEV_MP_NB_OBJS 1024
> #define CDEV_MP_CACHE_SZ 64
> #define MAX_QUEUE_PAIRS 1
>
> @@ -2003,10 +2002,11 @@ cryptodevs_init(uint16_t req_queue_num)
> dev_conf.ff_disable = RTE_CRYPTODEV_FF_ASYMMETRIC_CRYPTO;
>
> uint32_t dev_max_sess = cdev_info.sym.max_nb_sessions;
> - if (dev_max_sess != 0 && dev_max_sess < CDEV_MP_NB_OBJS)
> + if (dev_max_sess != 0 &&
> + dev_max_sess < get_nb_crypto_sessions())
> rte_exit(EXIT_FAILURE,
> "Device does not support at least %u "
> - "sessions", CDEV_MP_NB_OBJS);
> + "sessions", get_nb_crypto_sessions());
>
> if (rte_cryptodev_configure(cdev_id, &dev_conf))
> rte_panic("Failed to initialize cryptodev %u\n",
> @@ -2258,12 +2258,18 @@ session_pool_init(struct socket_ctx *ctx, int32_t socket_id, size_t sess_sz)
> {
> char mp_name[RTE_MEMPOOL_NAMESIZE];
> struct rte_mempool *sess_mp;
> + uint32_t nb_sess;
>
> snprintf(mp_name, RTE_MEMPOOL_NAMESIZE,
> "sess_mp_%u", socket_id);
> + /*
> + * Doubled due to rte_security_session_create() uses one mempool for
> + * session and for session private data.
> + */
> + nb_sess = (get_nb_crypto_sessions() + CDEV_MP_CACHE_SZ *
> + rte_lcore_count()) * 2;
> sess_mp = rte_cryptodev_sym_session_pool_create(
> - mp_name, CDEV_MP_NB_OBJS,
> - sess_sz, CDEV_MP_CACHE_SZ, 0,
> + mp_name, nb_sess, sess_sz, CDEV_MP_CACHE_SZ, 0,
> socket_id);
> ctx->session_pool = sess_mp;
>
> @@ -2280,11 +2286,18 @@ session_priv_pool_init(struct socket_ctx *ctx, int32_t socket_id,
> {
> char mp_name[RTE_MEMPOOL_NAMESIZE];
> struct rte_mempool *sess_mp;
> + uint32_t nb_sess;
>
> snprintf(mp_name, RTE_MEMPOOL_NAMESIZE,
> "sess_mp_priv_%u", socket_id);
> + /*
> + * Doubled due to rte_security_session_create() uses one mempool for
> + * session and for session private data.
> + */
> + nb_sess = (get_nb_crypto_sessions() + CDEV_MP_CACHE_SZ *
> + rte_lcore_count()) * 2;
> sess_mp = rte_mempool_create(mp_name,
> - CDEV_MP_NB_OBJS,
> + nb_sess,
> sess_sz,
> CDEV_MP_CACHE_SZ,
> 0, NULL, NULL, NULL,
> diff --git a/examples/ipsec-secgw/ipsec.h b/examples/ipsec-secgw/ipsec.h
> index 1f264c0..8ad3082 100644
> --- a/examples/ipsec-secgw/ipsec.h
> +++ b/examples/ipsec-secgw/ipsec.h
> @@ -409,4 +409,7 @@ int
> create_inline_session(struct socket_ctx *skt_ctx, struct ipsec_sa *sa,
> struct rte_ipsec_session *ips);
>
> +uint32_t
> +get_nb_crypto_sessions(void);
> +
> #endif /* __IPSEC_H__ */
> diff --git a/examples/ipsec-secgw/sa.c b/examples/ipsec-secgw/sa.c
> index a6bf5e8..2063db8 100644
> --- a/examples/ipsec-secgw/sa.c
> +++ b/examples/ipsec-secgw/sa.c
> @@ -135,6 +135,7 @@ const struct supported_aead_algo aead_algos[] = {
>
> #define SA_INIT_NB 128
>
> +static uint32_t nb_crypto_sessions;
> struct ipsec_sa *sa_out;
> uint32_t nb_sa_out;
> static uint32_t sa_out_sz;
> @@ -680,6 +681,7 @@ parse_sa_tokens(char **tokens, uint32_t n_tokens,
> }
>
> rule->fallback_sessions = 1;
> + nb_crypto_sessions++;
> fallback_p = 1;
> continue;
> }
> @@ -724,6 +726,7 @@ parse_sa_tokens(char **tokens, uint32_t n_tokens,
> rule->portid = -1;
> }
>
> + nb_crypto_sessions++;
> *ri = *ri + 1;
> }
>
> @@ -1542,3 +1545,9 @@ sa_sort_arr(void)
> qsort(sa_in, nb_sa_in, sizeof(struct ipsec_sa), sa_cmp);
> qsort(sa_out, nb_sa_out, sizeof(struct ipsec_sa), sa_cmp);
> }
> +
> +uint32_t
> +get_nb_crypto_sessions(void)
> +{
> + return nb_crypto_sessions;
> +}
> --
Tested-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 2.7.4
next prev parent reply other threads:[~2020-04-23 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 19:30 [dpdk-dev] [PATCH] " Vladimir Medvedkin
2020-04-14 14:17 ` [dpdk-dev] [PATCH v2] " Vladimir Medvedkin
2020-04-15 19:19 ` Akhil Goyal
2020-04-16 10:26 ` Medvedkin, Vladimir
2020-04-20 19:16 ` [dpdk-dev] [PATCH v3] " Vladimir Medvedkin
2020-04-23 0:12 ` Ananyev, Konstantin [this message]
2020-05-11 11:06 ` 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=BYAPR11MB3301C2EC1D564D021C7A5E279AD30@BYAPR11MB3301.namprd11.prod.outlook.com \
--to=konstantin.ananyev@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=vladimir.medvedkin@intel.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).