From: Akhil Goyal <gakhil@marvell.com>
To: Volodymyr Fialko <vfialko@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Radu Nicolau <radu.nicolau@intel.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
Volodymyr Fialko <vfialko@marvell.com>,
"konstantin.v.ananyev@yandex.ru" <konstantin.v.ananyev@yandex.ru>
Subject: RE: [PATCH 1/1] examples/ipsec-secgw: create lookaside sessions at init
Date: Wed, 11 May 2022 19:33:57 +0000 [thread overview]
Message-ID: <CO6PR18MB4484BC47F4C5176E78ADDA7AD8C89@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220427092020.2506177-1-vfialko@marvell.com>
> Subject: [PATCH 1/1] examples/ipsec-secgw: create lookaside sessions at init
>
> In event lookaside mode same session could be handled with multiple
> cores, and session creation in datapath will cause situation where
> multiple cores will try to create same session simultaneously.
> To avoid such case and enable event lookaside mode in future, lookaside
> sessions are now created at initialization in sa_add_rules().
>
> All sessions(inline and lookaside) now created during init process, so
> session pool information was removed from ipsec context. Core id was
> added to obtain correct crypto device queue pair for the current core.
>
> Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
> ---
> Depends-on: series-22265 ("examples/ipsec-secgw: examples/ipsec-secgw:
> destroy lookaside sessions")
> Depends-on: series-22593 ("examples/ipsec-secgw: move fast path helper
> functions")
Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto
prev parent reply other threads:[~2022-05-11 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 9:20 Volodymyr Fialko
2022-05-11 19:33 ` Akhil Goyal [this message]
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=CO6PR18MB4484BC47F4C5176E78ADDA7AD8C89@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=radu.nicolau@intel.com \
--cc=vfialko@marvell.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).