From patchwork Wed Aug 5 15:15:14 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Arkadiusz Kusztal X-Patchwork-Id: 75221 X-Patchwork-Delegate: thomas@monjalon.net Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 00496A053D; Wed, 5 Aug 2020 17:17:00 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D5FE82BF2; Wed, 5 Aug 2020 17:17:00 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 7B2F7E07 for ; Wed, 5 Aug 2020 17:16:59 +0200 (CEST) IronPort-SDR: mRVlctaYX/OlTsYLDO0flP/M5+R0+vNHMrhUbHINi+HpFqAXfiRTzkvBBC+9kJlXUrv5RPKr53 RhV3yVkplI2g== X-IronPort-AV: E=McAfee;i="6000,8403,9703"; a="214091139" X-IronPort-AV: E=Sophos;i="5.75,438,1589266800"; d="scan'208";a="214091139" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Aug 2020 08:16:58 -0700 IronPort-SDR: cKmSvzNFd0DKC2x8tfSN/vij/I6Fs6It8MUlv0DfZ5NzT+Wp6TL3VGBoOvRlKtj+X/YTS4Jylc G44MZ2WhCE7w== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,438,1589266800"; d="scan'208";a="306739595" Received: from unknown (HELO akusztax-MOBL1.ger.corp.intel.com) ([10.104.113.35]) by orsmga002.jf.intel.com with ESMTP; 05 Aug 2020 08:16:54 -0700 From: Arek Kusztal To: dev@dpdk.org Cc: akhil.goyal@nxp.com, anoobj@marvell.com, declan.doherty@intel.com, fiona.trahe@intel.com, asomalap@amd.com, rnagadheeraj@marvell.com, hemant.agrawal@nxp.com, pablo.de.lara.guarch@intel.com, roy.fan.zhang@intel.com, Arek Kusztal Date: Wed, 5 Aug 2020 17:15:14 +0200 Message-Id: <20200805151514.1180-1-arkadiuszx.kusztal@intel.com> X-Mailer: git-send-email 2.28.0.windows.1 MIME-Version: 1.0 Subject: [dpdk-dev] [PATCH v2] doc: announce move of aes gmac algorithm to aead 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" This patch announces removal of RTE_CRYPTO_AUTH_AES_GMAC from rte_crypto_auth_algorithm and addition of RTE_CRYPTO_AEAD_AES_GMAC to rte_crypto_aead_algorithm. AES-GMAC is variation of AES-GCM algorithm with the difference that it does not perform encryption. As a matter of fact internally there is no difference between GMAC and GCM except for the way how data is passed. Moving GMAC to AEAD can simplify way of implementing this alogrithm for example in IPsec (RFC4543). Signed-off-by: Arek Kusztal --- v2: - added description doc/guides/rel_notes/deprecation.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index ea4cfa7..6fe12b0 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -151,3 +151,7 @@ Deprecation Notices Python 2 support will be completely removed in 20.11. In 20.08, explicit deprecation warnings will be displayed when running scripts with Python 2. + +* cryptodev: ``RTE_CRYPTO_AUTH_AES_GMAC`` will no longer be included in + ``enum rte_crypto_auth_algorithm``. It will be included in + ``enum rte_crypto_aead_algorithm`` as ``RTE_CRYPTO_AEAD_AES_GMAC``.