<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>17ec3e71 - crypto: lib/Kconfig - Hide arch options from user</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#17ec3e71</link>
        <description>crypto: lib/Kconfig - Hide arch options from userThe ARCH_MAY_HAVE patch missed arm64, mips and s390.  But it mayalso lead to arch options being enabled but ineffective becauseof modular/built-in conflicts.As the primary user of all these options wireguard is selectingthe arch options anyway, make the same selections at the lib/cryptooption level and hide the arch options from the user.Instead of selecting them centrally from lib/crypto, simply setthe default of each arch option as suggested by Eric Biggers.Change the Crypto API generic algorithms to select the top-levellib/crypto options instead of the generic one as otherwise thereis no way to enable the arch options (Eric Biggers).  Introduce aset of INTERNAL options to work around dependency cycles on theCONFIG_CRYPTO symbol.Fixes: 1047e21aecdf (&quot;crypto: lib/Kconfig - Fix lib built-in failure when arch is modular&quot;)Reported-by: kernel test robot &lt;lkp@intel.com&gt;Reported-by: Arnd Bergmann &lt;arnd@kernel.org&gt;Closes: https://lore.kernel.org/oe-kbuild-all/202502232152.JC84YDLp-lkp@intel.com/Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Thu, 27 Feb 2025 07:48:39 +0000</pubDate>
        <dc:creator>Herbert Xu &lt;herbert@gondor.apana.org.au&gt;</dc:creator>
    </item>
<item>
        <title>1047e21a - crypto: lib/Kconfig - Fix lib built-in failure when arch is modular</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#1047e21a</link>
        <description>crypto: lib/Kconfig - Fix lib built-in failure when arch is modularThe HAVE_ARCH Kconfig options in lib/crypto try to solve themodular versus built-in problem, but it still fails when thethe LIB option (e.g., CRYPTO_LIB_CURVE25519) is selected externally.Fix this by introducing a level of indirection with ARCH_MAY_HAVEKconfig options, these then go on to select the ARCH_HAVE optionsif the ARCH Kconfig options matches that of the LIB option.Reported-by: kernel test robot &lt;lkp@intel.com&gt;Closes: https://lore.kernel.org/oe-kbuild-all/202501230223.ikroNDr1-lkp@intel.com/Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Wed, 12 Feb 2025 04:48:55 +0000</pubDate>
        <dc:creator>Herbert Xu &lt;herbert@gondor.apana.org.au&gt;</dc:creator>
    </item>
<item>
        <title>ed4bc981 - x86/crc-t10dif: expose CRC-T10DIF function through lib</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#ed4bc981</link>
        <description>x86/crc-t10dif: expose CRC-T10DIF function through libMove the x86 CRC-T10DIF assembly code into the lib directory and wire itup to the library interface.  This allows it to be used without goingthrough the crypto API.  It remains usable via the crypto API too viathe shash algorithms that use the library interface.  Thus all thearch-specific &quot;shash&quot; code becomes unnecessary and is removed.Reviewed-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;Reviewed-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;Link: https://lore.kernel.org/r/20241202012056.209768-5-ebiggers@kernel.orgSigned-off-by: Eric Biggers &lt;ebiggers@google.com&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Mon, 02 Dec 2024 01:20:48 +0000</pubDate>
        <dc:creator>Eric Biggers &lt;ebiggers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>55d1ecce - x86/crc32: expose CRC32 functions through lib</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#55d1ecce</link>
        <description>x86/crc32: expose CRC32 functions through libMove the x86 CRC32 assembly code into the lib directory and wire it upto the library interface.  This allows it to be used without goingthrough the crypto API.  It remains usable via the crypto API too viathe shash algorithms that use the library interface.  Thus all thearch-specific &quot;shash&quot; code becomes unnecessary and is removed.Reviewed-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;Link: https://lore.kernel.org/r/20241202010844.144356-14-ebiggers@kernel.orgSigned-off-by: Eric Biggers &lt;ebiggers@google.com&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Mon, 02 Dec 2024 01:08:38 +0000</pubDate>
        <dc:creator>Eric Biggers &lt;ebiggers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>af2aff7c - crypto: x86/aegis128 - optimize length block preparation using SSE4.1</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#af2aff7c</link>
        <description>crypto: x86/aegis128 - optimize length block preparation using SSE4.1Start using SSE4.1 instructions in the AES-NI AEGIS code, with the firstuse case being preparing the length block in fewer instructions.In practice this does not reduce the set of CPUs on which the code canrun, because all Intel and AMD CPUs with AES-NI also have SSE4.1.Upgrade the existing SSE2 feature check to SSE4.1, though it seems thischeck is not strictly necessary; the aesni-intel module has been gettingaway with using SSE4.1 despite checking for AES-NI only.Reviewed-by: Ondrej Mosnacek &lt;omosnace@redhat.com&gt;Signed-off-by: Eric Biggers &lt;ebiggers@google.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Thu, 17 Oct 2024 00:00:46 +0000</pubDate>
        <dc:creator>Eric Biggers &lt;ebiggers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>c299d7af - crypto: x86/aesni - update docs for aesni-intel module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#c299d7af</link>
        <description>crypto: x86/aesni - update docs for aesni-intel moduleUpdate the kconfig help and module description to reflect that VAESinstructions are now used in some cases.  Also fix XTR =&gt; XCTR.Signed-off-by: Eric Biggers &lt;ebiggers@google.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Tue, 27 Aug 2024 18:50:01 +0000</pubDate>
        <dc:creator>Eric Biggers &lt;ebiggers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>b06affb1 - crypto: x86/aes-gcm - add VAES and AVX512 / AVX10 optimized AES-GCM</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#b06affb1</link>
        <description>crypto: x86/aes-gcm - add VAES and AVX512 / AVX10 optimized AES-GCMAdd implementations of AES-GCM for x86_64 CPUs that support VAES (vectorAES), VPCLMULQDQ (vector carryless multiplication), and either AVX512 orAVX10.  There are two implementations, sharing most source code: oneusing 256-bit vectors and one using 512-bit vectors.  This patchimproves AES-GCM performance by up to 162%; see Tables 1 and 2 below.I wrote the new AES-GCM assembly code from scratch, focusing oncorrectness, performance, code size (both source and binary), anddocumenting the source.  The new assembly file aes-gcm-avx10-x86_64.S isabout 1200 lines including extensive comments, and it generates lessthan 8 KB of binary code.  The main loop does 4 vectors at a time, withthe AES and GHASH instructions interleaved.  Any remainder is handledusing a simple 1 vector at a time loop, with masking.Several VAES + AVX512 implementations of AES-GCM exist from Intel,including one in OpenSSL and one proposed for inclusion in Linux in 2021(https://lore.kernel.org/linux-crypto/1611386920-28579-6-git-send-email-megha.dey@intel.com/).These aren&apos;t really suitable to be used, though, due to the massiveamount of binary code generated (696 KB for OpenSSL, 200 KB for Linux)and well as the significantly larger amount of assembly source (4978lines for OpenSSL, 1788 lines for Linux).  Also, Intel&apos;s code does notsupport 256-bit vectors, which makes it not usable on futureAVX10/256-only CPUs, and also not ideal for certain Intel CPUs that havedownclocking issues.  So I ended up starting from scratch.  Usually mymuch shorter code is actually slightly faster than Intel&apos;s AVX512 code,though it depends on message length and on which of Intel&apos;simplementations is used; for details, see Tables 3 and 4 below.To facilitate potential integration into other projects, I&apos;vedual-licensed aes-gcm-avx10-x86_64.S under Apache-2.0 OR BSD-2-Clause,the same as the recently added RISC-V crypto code.The following two tables summarize the performance improvement over theexisting AES-GCM code in Linux that uses AES-NI and AVX2:Table 1: AES-256-GCM encryption throughput improvement,         CPU microarchitecture vs. message length in bytes:                      | 16384 |  4096 |  4095 |  1420 |   512 |   500 |----------------------+-------+-------+-------+-------+-------+-------+Intel Ice Lake        |   42% |   48% |   60% |   62% |   70% |   69% |Intel Sapphire Rapids |  157% |  145% |  162% |  119% |   96% |   96% |Intel Emerald Rapids  |  156% |  144% |  161% |  115% |   95% |  100% |AMD Zen 4             |  103% |   89% |   78% |   56% |   54% |   54% |                      |   300 |   200 |    64 |    63 |    16 |----------------------+-------+-------+-------+-------+-------+Intel Ice Lake        |   66% |   48% |   49% |   70% |   53% |Intel Sapphire Rapids |   80% |   60% |   41% |   62% |   38% |Intel Emerald Rapids  |   79% |   60% |   41% |   62% |   38% |AMD Zen 4             |   51% |   35% |   27% |   32% |   25% |Table 2: AES-256-GCM decryption throughput improvement,         CPU microarchitecture vs. message length in bytes:                      | 16384 |  4096 |  4095 |  1420 |   512 |   500 |----------------------+-------+-------+-------+-------+-------+-------+Intel Ice Lake        |   42% |   48% |   59% |   63% |   67% |   71% |Intel Sapphire Rapids |  159% |  145% |  161% |  125% |  102% |  100% |Intel Emerald Rapids  |  158% |  144% |  161% |  124% |  100% |  103% |AMD Zen 4             |  110% |   95% |   80% |   59% |   56% |   54% |                      |   300 |   200 |    64 |    63 |    16 |----------------------+-------+-------+-------+-------+-------+Intel Ice Lake        |   67% |   56% |   46% |   70% |   56% |Intel Sapphire Rapids |   79% |   62% |   39% |   61% |   39% |Intel Emerald Rapids  |   80% |   62% |   40% |   58% |   40% |AMD Zen 4             |   49% |   36% |   30% |   35% |   28% |The above numbers are percentage improvements in single-threadthroughput, so e.g. an increase from 4000 MB/s to 6000 MB/s would belisted as 50%.  They were collected by directly measuring the Linuxcrypto API performance using a custom kernel module.  Note that indirectbenchmarks (e.g. &apos;cryptsetup benchmark&apos; or benchmarking dm-crypt I/O)include more overhead and won&apos;t see quite as much of a difference.  Allthese benchmarks used an associated data length of 16 bytes.  Note thatAES-GCM is almost always used with short associated data lengths.The following two tables summarize how the performance of my codecompares with Intel&apos;s AVX512 AES-GCM code, both the version that is inOpenSSL and the version that was proposed for inclusion in Linux.Neither version exists in Linux currently, but these are alternativeAES-GCM implementations that could be chosen instead of mine.  Icollected the following numbers on Emerald Rapids using a userspacebenchmark program that calls the assembly functions directly.I&apos;ve also included a comparison with Cloudflare&apos;s AES-GCM implementationfrom https://boringssl-review.googlesource.com/c/boringssl/+/65987/3.Table 3: VAES-based AES-256-GCM encryption throughput in MB/s,         implementation name vs. message length in bytes:                     | 16384 |  4096 |  4095 |  1420 |   512 |   500 |---------------------+-------+-------+-------+-------+-------+-------+This implementation  | 14171 | 12956 | 12318 |  9588 |  7293 |  6449 |AVX512_Intel_OpenSSL | 14022 | 12467 | 11863 |  9107 |  5891 |  6472 |AVX512_Intel_Linux   | 13954 | 12277 | 11530 |  8712 |  6627 |  5898 |AVX512_Cloudflare    | 12564 | 11050 | 10905 |  8152 |  5345 |  5202 |                     |   300 |   200 |    64 |    63 |    16 |---------------------+-------+-------+-------+-------+-------+This implementation  |  4939 |  3688 |  1846 |  1821 |   738 |AVX512_Intel_OpenSSL |  4629 |  4532 |  2734 |  2332 |  1131 |AVX512_Intel_Linux   |  4035 |  2966 |  1567 |  1330 |   639 |AVX512_Cloudflare    |  3344 |  2485 |  1141 |  1127 |   456 |Table 4: VAES-based AES-256-GCM decryption throughput in MB/s,         implementation name vs. message length in bytes:                     | 16384 |  4096 |  4095 |  1420 |   512 |   500 |---------------------+-------+-------+-------+-------+-------+-------+This implementation  | 14276 | 13311 | 13007 | 11086 |  8268 |  8086 |AVX512_Intel_OpenSSL | 14067 | 12620 | 12421 |  9587 |  5954 |  7060 |AVX512_Intel_Linux   | 14116 | 12795 | 11778 |  9269 |  7735 |  6455 |AVX512_Cloudflare    | 13301 | 12018 | 11919 |  9182 |  7189 |  6726 |                     |   300 |   200 |    64 |    63 |    16 |---------------------+-------+-------+-------+-------+-------+This implementation  |  6454 |  5020 |  2635 |  2602 |  1079 |AVX512_Intel_OpenSSL |  5184 |  5799 |  2957 |  2545 |  1228 |AVX512_Intel_Linux   |  4394 |  4247 |  2235 |  1635 |   922 |AVX512_Cloudflare    |  4289 |  3851 |  1435 |  1417 |   574 |So, usually my code is actually slightly faster than Intel&apos;s code,though the OpenSSL implementation has a slight edge on messages shorterthan 256 bytes in this microbenchmark.  (This also holds true when doingthe same tests on AMD Zen 4.)  It can be seen that the large code size(up to 94x larger!) of the Intel implementations doesn&apos;t seem to bringmuch benefit, so starting from scratch with much smaller code, as I&apos;vedone, seems appropriate.  The performance of my code on messages shorterthan 256 bytes could be improved through a limited amount of unrolling,but it&apos;s unclear it would be worth it, given code size considerations(e.g. caches) that don&apos;t get measured in microbenchmarks.Signed-off-by: Eric Biggers &lt;ebiggers@google.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Sun, 02 Jun 2024 22:22:19 +0000</pubDate>
        <dc:creator>Eric Biggers &lt;ebiggers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>05bd1e2a - crypto: x86/sm4 - Remove cfb(sm4)</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#05bd1e2a</link>
        <description>crypto: x86/sm4 - Remove cfb(sm4)Remove the unused CFB implementation.Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Sat, 16 Sep 2023 09:16:52 +0000</pubDate>
        <dc:creator>Herbert Xu &lt;herbert@gondor.apana.org.au&gt;</dc:creator>
    </item>
<item>
        <title>d6b7ec11 - crypto: x86/aria-avx512 - fix build failure with old binutils</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#d6b7ec11</link>
        <description>crypto: x86/aria-avx512 - fix build failure with old binutilsThe minimum version of binutils for kernel build is currently 2.23 andit doesn&apos;t support GFNI.So, it fails to build the aria-avx512 if the old binutils is used.aria-avx512 requires GFNI, so it should not be allowed to build if theold binutils is used.The AS_AVX512 and AS_GFNI are added to the Kconfig to disable buildaria-avx512 if the old binutils is used.Fixes: c970d42001f2 (&quot;crypto: x86/aria - implement aria-avx512&quot;)Reported-by: Jan Beulich &lt;jbeulich@suse.com&gt;Signed-off-by: Taehee Yoo &lt;ap420073@gmail.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Sun, 15 Jan 2023 12:15:36 +0000</pubDate>
        <dc:creator>Taehee Yoo &lt;ap420073@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>c970d420 - crypto: x86/aria - implement aria-avx512</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#c970d420</link>
        <description>crypto: x86/aria - implement aria-avx512aria-avx512 implementation uses AVX512 and GFNI.It supports 64way parallel processing.So, byteslicing code is changed to support 64way parallel.And it exports some aria-avx2 functions such as encrypt() and decrypt().AVX and AVX2 have 16 registers.They should use memory to store/load state because of lack of registers.But AVX512 supports 32 registers.So, it doesn&apos;t require store/load in the s-box layer.It means that it can reduce overhead of store/load in the s-box layer.Also code become much simpler.Benchmark with modprobe tcrypt mode=610 num_mb=8192, i3-12100:ARIA-AVX512(128bit and 256bit)    testing speed of multibuffer ecb(aria) (ecb-aria-avx512) encryptiontcrypt: 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) decryptiontcrypt: 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) encryptiontcrypt: 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) decryptiontcrypt: 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)Signed-off-by: Taehee Yoo &lt;ap420073@gmail.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Sun, 01 Jan 2023 09:12:52 +0000</pubDate>
        <dc:creator>Taehee Yoo &lt;ap420073@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>37d8d3ae - crypto: x86/aria - implement aria-avx2</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#37d8d3ae</link>
        <description>crypto: x86/aria - implement aria-avx2aria-avx2 implementation uses AVX2, AES-NI, and GFNI.It supports 32way parallel processing.So, byteslicing code is changed to support 32way parallel.And it exports some aria-avx functions such as encrypt() and decrypt().There are two main logics, s-box layer and diffusion layer.These codes are the same as aria-avx implementation.But some instruction are exchanged because they don&apos;t support 256bitregisters.Also, AES-NI doesn&apos;t support 256bit register.So, aesenclast and aesdeclast are used twice like below:	vextracti128 $1, ymm0, xmm6;	vaesenclast xmm7, xmm0, xmm0;	vaesenclast xmm7, xmm6, xmm6;	vinserti128 $1, xmm6, ymm0, ymm0;Benchmark with modprobe tcrypt mode=610 num_mb=8192, i3-12100:ARIA-AVX2 with GFNI(128bit and 256bit)    testing speed of multibuffer ecb(aria) (ecb-aria-avx2) encryptiontcrypt: 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) decryptiontcrypt: 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) encryptiontcrypt: 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) decryptiontcrypt: 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)Signed-off-by: Taehee Yoo &lt;ap420073@gmail.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Sun, 01 Jan 2023 09:12:51 +0000</pubDate>
        <dc:creator>Taehee Yoo &lt;ap420073@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>ba3579e6 - crypto: aria-avx - add AES-NI/AVX/x86_64/GFNI assembler implementation of aria cipher</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#ba3579e6</link>
        <description>crypto: aria-avx - add AES-NI/AVX/x86_64/GFNI assembler implementation of aria cipherThe implementation is based on the 32-bit implementation of the aria.Also, aria-avx process steps are the similar to the camellia-avx.1. Byteslice(16way)2. Add-round-key.3. Sbox4. Diffusion layer.Except for s-box, all steps are the same as the aria-genericimplementation. s-box step is very similar to camellia andsm4 implementation.There are 2 implementations for s-box step.One is to use AES-NI and affine transformation, which is the same asCamellia, sm4, and others.Another is to use GFNI.GFNI implementation is faster than AES-NI implementation.So, it uses GFNI implementation if the running CPU supports GFNI.There are 4 s-boxes in the ARIA and the 2 s-boxes are the same asAES&apos;s s-boxes.To calculate the first sbox, it just uses the aesenclast and theninverts shift_row.No more process is needed for this job because the first s-box isthe same as the AES encryption s-box.To calculate the second sbox(invert of s1), it just uses the aesdeclastand then inverts shift_row.No more process is needed for this job because the second s-box isthe same as the AES decryption s-box.To calculate the third s-box, it uses the aesenclast,then affine transformation, which is combined AES inverse affine andARIA S2.To calculate the last s-box, it uses the aesdeclast,then affine transformation, which is combined X2 and AES forward affine.The optimized third and last s-box logic and GFNI s-box logic areimplemented by Jussi Kivilinna.The aria-generic implementation is based on a 32-bit implementation,not an 8-bit implementation. the aria-avx Diffusion Layer implementationis based on aria-generic implementation because 8-bit implementation isnot fit for parallel implementation but 32-bit is enough to fit for this.Signed-off-by: Taehee Yoo &lt;ap420073@gmail.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Fri, 16 Sep 2022 12:57:35 +0000</pubDate>
        <dc:creator>Taehee Yoo &lt;ap420073@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>cf514b2a - crypto: Kconfig - simplify cipher entries</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#cf514b2a</link>
        <description>crypto: Kconfig - simplify cipher entriesShorten menu titles and make them consistent:- acronym- name- architecture features in parenthesis- no suffixes like &quot;&lt;something&gt; algorithm&quot;, &quot;support&quot;, or  &quot;hardware acceleration&quot;, or &quot;optimized&quot;Simplify help text descriptions, update references, and ensure thathttps references are still valid.Signed-off-by: Robert Elliott &lt;elliott@hpe.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Sat, 20 Aug 2022 18:41:50 +0000</pubDate>
        <dc:creator>Robert Elliott &lt;elliott@hpe.com&gt;</dc:creator>
    </item>
<item>
        <title>3f342a23 - crypto: Kconfig - simplify hash entries</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#3f342a23</link>
        <description>crypto: Kconfig - simplify hash entriesShorten menu titles and make them consistent:- acronym- name- architecture features in parenthesis- no suffixes like &quot;&lt;something&gt; algorithm&quot;, &quot;support&quot;, or  &quot;hardware acceleration&quot;, or &quot;optimized&quot;Simplify help text descriptions, update references, and ensure thathttps references are still valid.Signed-off-by: Robert Elliott &lt;elliott@hpe.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Sat, 20 Aug 2022 18:41:48 +0000</pubDate>
        <dc:creator>Robert Elliott &lt;elliott@hpe.com&gt;</dc:creator>
    </item>
<item>
        <title>e3d2eadd - crypto: Kconfig - simplify aead entries</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#e3d2eadd</link>
        <description>crypto: Kconfig - simplify aead entriesShorten menu titles and make them consistent:- acronym- name- architecture features in parenthesis- no suffixes like &quot;&lt;something&gt; algorithm&quot;, &quot;support&quot;, or  &quot;hardware acceleration&quot;, or &quot;optimized&quot;Simplify help text descriptions, update references, and ensure thathttps references are still valid.Signed-off-by: Robert Elliott &lt;elliott@hpe.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Sat, 20 Aug 2022 18:41:47 +0000</pubDate>
        <dc:creator>Robert Elliott &lt;elliott@hpe.com&gt;</dc:creator>
    </item>
<item>
        <title>ec84348d - crypto: Kconfig - simplify CRC entries</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#ec84348d</link>
        <description>crypto: Kconfig - simplify CRC entriesShorten menu titles and make them consistent:- acronym- name- architecture features in parenthesis- no suffixes like &quot;&lt;something&gt; algorithm&quot;, &quot;support&quot;, or  &quot;hardware acceleration&quot;, or &quot;optimized&quot;Simplify help text descriptions, update references, and ensure thathttps references are still valid.Signed-off-by: Robert Elliott &lt;elliott@hpe.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Sat, 20 Aug 2022 18:41:46 +0000</pubDate>
        <dc:creator>Robert Elliott &lt;elliott@hpe.com&gt;</dc:creator>
    </item>
<item>
        <title>05b37465 - crypto: Kconfig - simplify public-key entries</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#05b37465</link>
        <description>crypto: Kconfig - simplify public-key entriesShorten menu titles and make them consistent:- acronym- name- architecture features in parenthesis- no suffixes like &quot;&lt;something&gt; algorithm&quot;, &quot;support&quot;, or  &quot;hardware acceleration&quot;, or &quot;optimized&quot;Simplify help text descriptions, update references, and ensure thathttps references are still valid.Signed-off-by: Robert Elliott &lt;elliott@hpe.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Sat, 20 Aug 2022 18:41:45 +0000</pubDate>
        <dc:creator>Robert Elliott &lt;elliott@hpe.com&gt;</dc:creator>
    </item>
<item>
        <title>28a936ef - crypto: Kconfig - move x86 entries to a submenu</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/crypto/Kconfig#28a936ef</link>
        <description>crypto: Kconfig - move x86 entries to a submenuMove CPU-specific crypto/Kconfig entries to arch/xxx/crypto/Kconfigand create a submenu for them under the Crypto API menu.Suggested-by: Eric Biggers &lt;ebiggers@kernel.org&gt;Signed-off-by: Robert Elliott &lt;elliott@hpe.com&gt;Signed-off-by: Herbert Xu &lt;herbert@gondor.apana.org.au&gt;

            List of files:
            /linux-6.15/arch/x86/crypto/Kconfig</description>
        <pubDate>Sat, 20 Aug 2022 18:41:39 +0000</pubDate>
        <dc:creator>Robert Elliott &lt;elliott@hpe.com&gt;</dc:creator>
    </item>
</channel>
</rss>
