From: "Coyle, David" <david.coyle@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"Nicolau, Radu" <radu.nicolau@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"adwivedi@marvell.com" <adwivedi@marvell.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add deprecation notice for security session create API
Date: Fri, 31 Jul 2020 09:29:07 +0000 [thread overview]
Message-ID: <MN2PR11MB35501BF6A9C0E558580F4390E34E0@MN2PR11MB3550.namprd11.prod.outlook.com> (raw)
> 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>
> ---
> doc/guides/rel_notes/deprecation.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
Acked-by: David Coyle <david.coyle@intel.com>
next reply other threads:[~2020-07-31 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 9:29 Coyle, David [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-30 17:13 Akhil Goyal
2020-07-30 17:17 ` Hemant Agrawal
2020-07-31 9:58 ` Ananyev, Konstantin
2020-08-06 16:19 ` Thomas Monjalon
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=MN2PR11MB35501BF6A9C0E558580F4390E34E0@MN2PR11MB3550.namprd11.prod.outlook.com \
--to=david.coyle@intel.com \
--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 \
--cc=thomas@monjalon.net \
/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).