From: Thomas Monjalon <thomas@monjalon.net>
To: Akhil Goyal <akhil.goyal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"adwivedi@marvell.com" <adwivedi@marvell.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add deprecation notice for security session create API
Date: Thu, 06 Aug 2020 18:19:17 +0200 [thread overview]
Message-ID: <6216584.A8hVyRZat7@thomas> (raw)
In-Reply-To: <BYAPR11MB3301C810FCAD39A32B78CC7B9A4E0@BYAPR11MB3301.namprd11.prod.outlook.com>
> > The API ``rte_security_session_create`` takes only single mempool
> > for session and session private data. So the application need to create
> > mempool for twice the number of sessions needed and will also lead to
> > wastage of memory as session private data need more memory compared to session.
> > Hence the API will be modified to take two mempool pointers - one for session
> > and one for private data. This is very similar to crypto based session
> > create APIs.
> >
> > Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
> > ---
> > +* security: The API ``rte_security_session_create`` takes only single mempool
> > + for session and session private data. So the application need to create
> > + mempool for twice the number of sessions needed and will also lead to
> > + wastage of memory as session private data need more memory compared to session.
> > + Hence the API will be modified to take two mempool pointers - one for session
> > + and one for private data.
> > +
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> Acked-by: Anoob Joseph <anoobj@marvell.com>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Applied
next prev parent reply other threads:[~2020-08-06 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 17:13 Akhil Goyal
2020-07-30 17:17 ` Hemant Agrawal
2020-07-30 17:26 ` [dpdk-dev] [EXT] " Anoob Joseph
2020-07-31 9:58 ` [dpdk-dev] " Ananyev, Konstantin
2020-08-06 16:19 ` Thomas Monjalon [this message]
2020-07-31 9:29 Coyle, David
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=6216584.A8hVyRZat7@thomas \
--to=thomas@monjalon.net \
--cc=adwivedi@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=konstantin.ananyev@intel.com \
--cc=radu.nicolau@intel.com \
--cc=roy.fan.zhang@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).