Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp9333130rwl; Sun, 1 Jan 2023 01:18:31 -0800 (PST) X-Google-Smtp-Source: AMrXdXsiex1dM7V+LbfWQ9u8MJP5MrcnfZdtjDZyGjTdoZKIaTaRONv21IEn6eZikaIOROoNvdP2 X-Received: by 2002:a05:6a20:c186:b0:af:74f5:93a3 with SMTP id bg6-20020a056a20c18600b000af74f593a3mr46423302pzb.61.1672564711031; Sun, 01 Jan 2023 01:18:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672564711; cv=none; d=google.com; s=arc-20160816; b=iAI/ZzC9A7qGnG6T8vZXTzUiIKa5anWv5+3pxKLNyEvIZKrFHBLMjkm8QiPSUOBwYN d5uA/IxT4epT1JQhOSF8ZtHSKKpf2LlkRrcDIyRrlPBhTKZ2Lz6fhY6flqI8n0QuLKbB qB/uTQwRg+epysPgFhvJxs8165RrngTAs1T5Mx9IA4sHnbMMekows3Fvsn0fVqxlArkj 2mRROfeu3CY6VTS7GB0G/n+0yygae+pn8lnnuEnV77lU/DPSXMBtcDvuwrimo34npgqA IwtcGbAd9DquuafYlwoMPGgh1ofXs6VOMqntIgDgLnOHUQLZJ26daG8y/Gt02U5OZlYv FzAA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=Is4k+gx3KJfrIFoJwvzCiaGbFwIyqTDsgClxLrk5UJQ=; b=kwQI6cx684m1TTlNrn6HQxcf0sml+amodegkc2D0VSpuHjgYCDCeEaqbFBGRhRU6HR J5XhoU1TSLinpxpvxFLdnxLQx2XGUAsACGwNkM5fpF1elfdCU+3J9wLOLoFbYwopvbN8 rOb0VjpI2974LbuVuZr6tfAxYyq2v0LYksMtI981XkZad6Ia9GQPaIDDpfKe+dbSD49Q GjVo2P8YLf01tzj6DbrgbLVaTIbkMP6MBzJ+AEarRDwsgykl5hxV/+9+4xrVjUn/9Qv3 EZRbr1Um6oVV3FZYsATxFWjasVqhlkifoIg1bdaqPrHlWV6hpguZ17sQdy7gPcUm134L ZcWw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=NlFz9Ncx; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e37-20020a635465000000b00476f43ccfa8si27618356pgm.849.2023.01.01.01.18.17; Sun, 01 Jan 2023 01:18:31 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=NlFz9Ncx; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229558AbjAAJNI (ORCPT + 99 others); Sun, 1 Jan 2023 04:13:08 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43042 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229476AbjAAJNH (ORCPT ); Sun, 1 Jan 2023 04:13:07 -0500 Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3F1E15F7B for ; Sun, 1 Jan 2023 01:13:06 -0800 (PST) Received: by mail-pf1-x431.google.com with SMTP id 124so17032586pfy.0 for ; Sun, 01 Jan 2023 01:13:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=Is4k+gx3KJfrIFoJwvzCiaGbFwIyqTDsgClxLrk5UJQ=; b=NlFz9NcxV1wINEXt3iDPnKE/6hDLG0FDx/TtqC0Ms4cy7s+enWHjESCev76+j2a5GH pmcW68VgTXRmsZYTgLF1S0uRSl6UQQQ9vXPOwPW8P0dvBt61a51BTZvXTV3mjP4GF9op WtT7qHLZo9oas9v+45aMnLf8PMAM0ZigwAaQMlaUMjKGxtnFLKoAo+GBfUD+sCw9nR/F 08dje3tOMh0wwT8aMaXpe5XSkHeb5rhxY2JFXpTZ8vA6idOxjsJcbduX/x/9obpw037N oFMlaRZRXr4YQiMHMtDaqiMAmwaZkxaKKdgsUQKf2s47rT1KYhkKWUEuWC9P9dj4Qaly wB7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Is4k+gx3KJfrIFoJwvzCiaGbFwIyqTDsgClxLrk5UJQ=; b=rAm1afFk37yUTcQPRI9O8qt/SvN0XWjMcBm5DcLafFbEW5WnvV+uBmVXO5tiwsc+lK cUoYZkU8zzOBRTQfSSn/REKVo4KOc/zi/H3Z5B0CNDbX1gbsg2w4R6cn7MUoCNjUW/Rv I5t2zaHMfTg5OVhBNU2M6dcY/r4gw4G/3WwD4UvjxIkjqs3ScqkdDHVJGvuVHwg9+fB7 Gb+oQVWfVry/LddZAws9hW3AjFjhV7bk5q6bpq33sgPHCVIaI3V0e9UVX46bVu1k7nti NeTwE14JWK9MX24KQUEQe2QTgWANnCabwns1OHUXZD2BUGejlXTKnUJcMhooYNQ8RP9w mcsA== X-Gm-Message-State: AFqh2ko2qKkFPOXynLcDe04nOY0ITs25YzNwbNyVgYJFJ7eFDgL+5348 sg0N+zzKwamZawf1RGocoTYyUvCOuUrFuA== X-Received: by 2002:aa7:8a42:0:b0:582:34f2:20f1 with SMTP id n2-20020aa78a42000000b0058234f220f1mr4377436pfa.11.1672564384878; Sun, 01 Jan 2023 01:13:04 -0800 (PST) Received: from ap.. ([182.213.254.91]) by smtp.gmail.com with ESMTPSA id k26-20020aa79d1a000000b0058130f1eca1sm10951327pfp.182.2023.01.01.01.13.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 01 Jan 2023 01:13:03 -0800 (PST) From: Taehee Yoo To: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au, davem@davemloft.net, x86@kernel.org Cc: elliott@hpe.com, jussi.kivilinna@iki.fi, ebiggers@kernel.org, ap420073@gmail.com Subject: [PATCH v8 0/4] crypto: aria: implement aria-avx2 and aria-avx512 Date: Sun, 1 Jan 2023 09:12:48 +0000 Message-Id: <20230101091252.700117-1-ap420073@gmail.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org This patchset is to implement aria-avx2 and aria-avx512. There are some differences between aria-avx, aria-avx2, and aria-avx512, but they are not core logic(s-box, diffusion layer). ARIA-AVX2 It supports 32way parallel processing using 256bit registers. Like ARIA-AVX, it supports both AES-NI based s-box layer algorithm and GFNI based s-box layer algorithm. These algorithms are the same as ARIA-AVX except that AES-NI doesn't support 256bit registers, so it is used twice. ARIA-AVX512 It supports 64way parallel processing using 512bit registers. It supports only GFNI based s-box layer algorithm. Benchmarks with i3-12100 commands: modprobe tcrypt mode=610 num_mb=8192 ARIA-AVX512(128bit and 256bit) testing speed of multibuffer ecb(aria) (ecb-aria-avx512) encryption tcrypt: 1 operation in 1504 cycles (1024 bytes) tcrypt: 1 operation in 4595 cycles (4096 bytes) tcrypt: 1 operation in 1763 cycles (1024 bytes) tcrypt: 1 operation in 5540 cycles (4096 bytes) testing speed of multibuffer ecb(aria) (ecb-aria-avx512) decryption tcrypt: 1 operation in 1502 cycles (1024 bytes) tcrypt: 1 operation in 4615 cycles (4096 bytes) tcrypt: 1 operation in 1759 cycles (1024 bytes) tcrypt: 1 operation in 5554 cycles (4096 bytes) ARIA-AVX2 with GFNI(128bit and 256bit) testing speed of multibuffer ecb(aria) (ecb-aria-avx2) encryption tcrypt: 1 operation in 2003 cycles (1024 bytes) tcrypt: 1 operation in 5867 cycles (4096 bytes) tcrypt: 1 operation in 2358 cycles (1024 bytes) tcrypt: 1 operation in 7295 cycles (4096 bytes) testing speed of multibuffer ecb(aria) (ecb-aria-avx2) decryption tcrypt: 1 operation in 2004 cycles (1024 bytes) tcrypt: 1 operation in 5956 cycles (4096 bytes) tcrypt: 1 operation in 2409 cycles (1024 bytes) tcrypt: 1 operation in 7564 cycles (4096 bytes) ARIA-AVX with GFNI(128bit and 256bit) testing speed of multibuffer ecb(aria) (ecb-aria-avx) encryption tcrypt: 1 operation in 2761 cycles (1024 bytes) tcrypt: 1 operation in 9390 cycles (4096 bytes) tcrypt: 1 operation in 3401 cycles (1024 bytes) tcrypt: 1 operation in 11876 cycles (4096 bytes) testing speed of multibuffer ecb(aria) (ecb-aria-avx) decryption tcrypt: 1 operation in 2735 cycles (1024 bytes) tcrypt: 1 operation in 9424 cycles (4096 bytes) tcrypt: 1 operation in 3369 cycles (1024 bytes) tcrypt: 1 operation in 11954 cycles (4096 bytes) v8: - Remove unnecessary code in aria-gfni-avx512-asm_64.S - Do not use magic numbers in the aria-avx.h - Rebase v7: - Use IS_ENABLED() instead of defined() v6: - Rebase for "CFI fixes" patchset. - Use SYM_TYPED_FUNC_START instead of SYM_FUNC_START. v5: - Set CRYPTO_ALG_SKCIPHER_REQSIZE_LARGE flag to avx2, and avx512. v4: - Use keystream array in the request ctx. v3: - Use ARIA_CTX_enc_key, ARIA_CTX_dec_key, and ARIA_CTX_rounds defines. v2: - Add new "add keystream array into struct aria_ctx" patch. - Use keystream array in the aria_ctx instead of stack memory Taehee Yoo (4): crypto: aria: add keystream array into request ctx crypto: aria: do not use magic number offsets of aria_ctx crypto: aria: implement aria-avx2 crypto: aria: implement aria-avx512 arch/x86/crypto/Kconfig | 38 + arch/x86/crypto/Makefile | 6 + arch/x86/crypto/aria-aesni-avx-asm_64.S | 26 +- arch/x86/crypto/aria-aesni-avx2-asm_64.S | 1433 +++++++++++++++++++++ arch/x86/crypto/aria-avx.h | 48 +- arch/x86/crypto/aria-gfni-avx512-asm_64.S | 971 ++++++++++++++ arch/x86/crypto/aria_aesni_avx2_glue.c | 252 ++++ arch/x86/crypto/aria_aesni_avx_glue.c | 45 +- arch/x86/crypto/aria_gfni_avx512_glue.c | 250 ++++ arch/x86/kernel/asm-offsets.c | 8 + crypto/aria_generic.c | 4 + 11 files changed, 3052 insertions(+), 29 deletions(-) create mode 100644 arch/x86/crypto/aria-aesni-avx2-asm_64.S create mode 100644 arch/x86/crypto/aria-gfni-avx512-asm_64.S create mode 100644 arch/x86/crypto/aria_aesni_avx2_glue.c create mode 100644 arch/x86/crypto/aria_gfni_avx512_glue.c -- 2.34.1