From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 654BD45BA5; Tue, 22 Oct 2024 22:21:00 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4313840151; Tue, 22 Oct 2024 22:20:57 +0200 (CEST) Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.9]) by mails.dpdk.org (Postfix) with ESMTP id 6FBA640151 for ; Tue, 22 Oct 2024 22:20:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1729628455; x=1761164455; h=from:to:cc:subject:date:message-id:in-reply-to: references; bh=Kgd29zgJ1cNYmc7xdq5EWkw0a/vrB5abn6HX7B4JaJ0=; b=Eo751MOAAXwRtyRwElGHopch4TYaPsopKceAyL0B5jkwa+lMDc8VfNfI dQmIXllivIavCwa69SL0h2kY6KHJAFsSH6FxaPrOSwWfzNJN/Z+HWJAL1 yOFnYpu8VByjjvdTb8PArO3pEw+/C2uvFqKc/0CULmBMh60qdyBN1p6xc 9b5hYRdP633aqIDji7ccjA9b2khCLvEZ4+iBt1tATjeQ+Q/sQb16DAM0S QdWvc9pyYeqxH9BwA1griA2SZSrRxpETWeE2jvz515Px3QQNKCF4JLdEo hF28wLwpU7YOa83C/gDT+JCmt1qj3rxrJ1Q1idmgqof6N06rcK88J4may g==; X-CSE-ConnectionGUID: iRMbtneQRB+rx8yC5EFzYw== X-CSE-MsgGUID: kaWtn2ZdRaiv+JimyRQ05w== X-IronPort-AV: E=McAfee;i="6700,10204,11233"; a="39808391" X-IronPort-AV: E=Sophos;i="6.11,223,1725346800"; d="scan'208";a="39808391" Received: from fmviesa004.fm.intel.com ([10.60.135.144]) by fmvoesa103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Oct 2024 13:20:54 -0700 X-CSE-ConnectionGUID: eXoRqdc5TT+1/AePBejkeQ== X-CSE-MsgGUID: hctlLkoTSrW/uS/tNNb18Q== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.11,223,1725346800"; d="scan'208";a="84598529" Received: from silpixa00399302.ir.intel.com ([10.237.214.22]) by fmviesa004.fm.intel.com with ESMTP; 22 Oct 2024 13:20:53 -0700 From: Arkadiusz Kusztal To: dev@dpdk.org Cc: gakhil@marvell.com, brian.dooley@intel.com, Arkadiusz Kusztal Subject: [PATCH v6 1/3] cryptodev: add ec points to sm2 op Date: Tue, 22 Oct 2024 20:05:58 +0100 Message-Id: <20241022190600.81169-2-arkadiuszx.kusztal@intel.com> X-Mailer: git-send-email 2.13.6 In-Reply-To: <20241022190600.81169-1-arkadiuszx.kusztal@intel.com> References: <20241022190600.81169-1-arkadiuszx.kusztal@intel.com> X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org In the case when PMD cannot support the full process of the SM2, but elliptic curve computation only, additional fields are needed to handle such a case. Points C1, kP therefore were added to the SM2 crypto operation struct. Signed-off-by: Arkadiusz Kusztal --- doc/guides/rel_notes/release_24_11.rst | 3 ++ lib/cryptodev/rte_crypto_asym.h | 56 +++++++++++++++++++------- 2 files changed, 45 insertions(+), 14 deletions(-) diff --git a/doc/guides/rel_notes/release_24_11.rst b/doc/guides/rel_notes/release_24_11.rst index fa4822d928..0f91dae987 100644 --- a/doc/guides/rel_notes/release_24_11.rst +++ b/doc/guides/rel_notes/release_24_11.rst @@ -406,6 +406,9 @@ ABI Changes added new structure ``rte_node_xstats`` to ``rte_node_register`` and added ``xstat_off`` to ``rte_node``. +* cryptodev: The ``rte_crypto_sm2_op_param`` struct member to hold ciphertext + is changed to union data type. This change is to support partial SM2 calculation. + Known Issues ------------ diff --git a/lib/cryptodev/rte_crypto_asym.h b/lib/cryptodev/rte_crypto_asym.h index aeb46e688e..f095cebcd0 100644 --- a/lib/cryptodev/rte_crypto_asym.h +++ b/lib/cryptodev/rte_crypto_asym.h @@ -646,6 +646,8 @@ enum rte_crypto_sm2_op_capa { /**< Random number generator supported in SM2 ops. */ RTE_CRYPTO_SM2_PH, /**< Prehash message before crypto op. */ + RTE_CRYPTO_SM2_PARTIAL, + /**< Calculate elliptic curve points only. */ }; /** @@ -673,20 +675,46 @@ struct rte_crypto_sm2_op_param { * will be overwritten by the PMD with the decrypted length. */ - rte_crypto_param cipher; - /**< - * Pointer to input data - * - to be decrypted for SM2 private decrypt. - * - * Pointer to output data - * - for SM2 public encrypt. - * In this case the underlying array should have been allocated - * with enough memory to hold ciphertext output (at least X bytes - * for prime field curve of N bytes and for message M bytes, - * where X = (C1 || C2 || C3) and computed based on SM2 RFC as - * C1 (1 + N + N), C2 = M, C3 = N. The cipher.length field will - * be overwritten by the PMD with the encrypted length. - */ + union { + rte_crypto_param cipher; + /**< + * Pointer to input data + * - to be decrypted for SM2 private decrypt. + * + * Pointer to output data + * - for SM2 public encrypt. + * In this case the underlying array should have been allocated + * with enough memory to hold ciphertext output (at least X bytes + * for prime field curve of N bytes and for message M bytes, + * where X = (C1 || C2 || C3) and computed based on SM2 RFC as + * C1 (1 + N + N), C2 = M, C3 = N. The cipher.length field will + * be overwritten by the PMD with the encrypted length. + */ + struct { + struct rte_crypto_ec_point c1; + /**< + * This field is used only when PMD does not support the full + * process of the SM2 encryption/decryption, but the elliptic + * curve part only. + * + * In the case of encryption, it is an output - point C1 = (x1,y1). + * In the case of decryption, if is an input - point C1 = (x1,y1). + * + * Must be used along with the RTE_CRYPTO_SM2_PARTIAL flag. + */ + struct rte_crypto_ec_point kp; + /**< + * This field is used only when PMD does not support the full + * process of the SM2 encryption/decryption, but the elliptic + * curve part only. + * + * It is an output in the encryption case, it is a point + * [k]P = (x2,y2). + * + * Must be used along with the RTE_CRYPTO_SM2_PARTIAL flag. + */ + }; + }; rte_crypto_uint id; /**< The SM2 id used by signer and verifier. */ -- 2.17.1