[dpdk-dev] [PATCH] doc: add deprecation notice for security session create API
Akhil Goyal
akhil.goyal at nxp.com
Thu Jul 30 19:13:30 CEST 2020
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 at nxp.com>
---
doc/guides/rel_notes/deprecation.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index ea4cfa7a4..9ed7b55e6 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -126,6 +126,13 @@ Deprecation Notices
to one it means it represents IV, when is set to zero it means J0 is used
directly, in this case 16 bytes of J0 need to be passed.
+* 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.
+
* sched: To allow more traffic classes, flexible mapping of pipe queues to
traffic classes, and subport level configuration of pipes and queues
changes will be made to macros, data structures and API functions defined
--
2.17.1
More information about the dev
mailing list