From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id B08EDA052B; Thu, 30 Jul 2020 19:13:44 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 91F1B4C93; Thu, 30 Jul 2020 19:13:44 +0200 (CEST) Received: from inva020.nxp.com (inva020.nxp.com [92.121.34.13]) by dpdk.org (Postfix) with ESMTP id 104A6A69 for ; Thu, 30 Jul 2020 19:13:44 +0200 (CEST) Received: from inva020.nxp.com (localhost [127.0.0.1]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id AFEBB1A1393; Thu, 30 Jul 2020 19:13:43 +0200 (CEST) Received: from invc005.ap-rdc01.nxp.com (invc005.ap-rdc01.nxp.com [165.114.16.14]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id 4589E1A0438; Thu, 30 Jul 2020 19:13:39 +0200 (CEST) Received: from lsv03273.swis.in-blr01.nxp.com (lsv03273.swis.in-blr01.nxp.com [92.120.147.113]) by invc005.ap-rdc01.nxp.com (Postfix) with ESMTP id C12F040310; Thu, 30 Jul 2020 19:13:33 +0200 (CEST) From: Akhil Goyal To: dev@dpdk.org, anoobj@marvell.com, radu.nicolau@intel.com, konstantin.ananyev@intel.com, declan.doherty@intel.com, roy.fan.zhang@intel.com Cc: thomas@monjalon.net, fiona.trahe@intel.com, adwivedi@marvell.com, hemant.agrawal@nxp.com, Akhil Goyal Date: Thu, 30 Jul 2020 22:43:30 +0530 Message-Id: <20200730171330.16144-1-akhil.goyal@nxp.com> X-Mailer: git-send-email 2.17.1 X-Virus-Scanned: ClamAV using ClamSMTP Subject: [dpdk-dev] [PATCH] doc: add deprecation notice for security session create API X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 --- 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