| /linux/crypto/ |
| H A D | Kconfig | 3 # Generic algorithms support
59 This option provides the API for cryptographic algorithms.
173 registration time if algorithms are dynamically loaded later.
197 tristate "Null algorithms"
202 These are 'Null' algorithms, used by IPsec, which do nothing.
258 algorithms in the kernel. It should not be enabled in production
341 One of the Russian cryptographic standard algorithms (called GOST
342 algorithms). Only signature verification is implemented.
364 AES cipher algorithms (Rijndael)(FIPS-197, ISO/IEC 18033-3)
429 Camellia cipher algorithms (ISO/IEC 18033-3)
[all …]
|
| /linux/Documentation/admin-guide/blockdev/ |
| H A D | zram.rst | 80 currently selected (shown in square brackets) compression algorithms,
86 #show supported compression algorithms
94 algorithms that are supported by zram.
99 Compression algorithms may support specific parameters which can be
103 For example, several compression algorithms support `level` parameter.
104 In addition, certain compression algorithms support pre-trained dictionaries,
105 which significantly change algorithms' characteristics. In order to configure
120 Parameters are algorithm specific: not all algorithms support pre-trained
121 dictionaries, not all algorithms support `level`. Furthermore, for certain
122 algorithms `level` controls the compression level (the higher the value the
[all …]
|
| /linux/Documentation/crypto/ |
| H A D | api-intro.rst | 23 At the lowest level are algorithms, which register dynamically with the
28 abstraction to the underlying algorithms. However, at the user
35 [algorithm api] (for registering algorithms)
100 Adding New Algorithms
112 Algorithms submitted must also be generally patent-free (e.g. IDEA
117 Also check for any RFCs which may relate to the use of specific algorithms,
119 Cipher Algorithms").
188 Original developers of the crypto algorithms:
|
| H A D | devel-algos.rst | 1 Developing Cipher Algorithms
40 successfully registered all the given algorithms; if it fails partway
44 return value. Don't try to unregister algorithms that aren't
111 The registration of multi-block cipher algorithms is one of the most
|
| H A D | intro.rst | 18 The kernel crypto API refers to all algorithms as "transformations".
34 transformations (such as CRC or even compression algorithms) that can
|
| /linux/net/ipv6/ |
| H A D | Kconfig | 53 AH can be used with various authentication algorithms. Besides
55 implementations of the algorithms that RFC 8221 lists as MUST be
56 implemented. If you need any other algorithms, you'll need to enable
58 implementations of any needed algorithms when available.
68 ESP can be used with various encryption and authentication algorithms.
70 implementations of the algorithms that RFC 8221 lists as MUST be
71 implemented. If you need any other algorithms, you'll need to enable
73 implementations of any needed algorithms when available.
|
| /linux/Documentation/filesystems/ |
| H A D | btrfs.rst | 21 * Checksums on data and metadata (multiple algorithms available)
22 * Compression (multiple algorithms available)
26 * Integrated multiple device support, with several raid algorithms
|
| /linux/drivers/crypto/intel/keembay/ |
| H A D | Kconfig | 73 sm3, as well as the HMAC variant of these algorithms.
84 Enables support for sha224 and hmac(sha224) algorithms in the Intel
86 algorithms.
|
| /linux/include/linux/ |
| H A D | crc8.h | 46 * regular bit order (lsb first). Polynomials in CRC algorithms are typically
64 * reverse bit order (msb first). Polynomials in CRC algorithms are typically
95 * "A Painless Guide to CRC Error Detection Algorithms", ver 3, Aug 1993
|
| /linux/Documentation/devicetree/bindings/crypto/ |
| H A D | nvidia,tegra234-se-aes.yaml | 7 title: NVIDIA Tegra Security Engine for AES algorithms
11 algorithms - AES-ECB, AES-CBC, AES-OFB, AES-XTS, AES-CTR, AES-GCM, AES-CCM,
|
| /linux/net/ipv4/ |
| H A D | Kconfig | 345 AH can be used with various authentication algorithms. Besides
347 implementations of the algorithms that RFC 8221 lists as MUST be
348 implemented. If you need any other algorithms, you'll need to enable
350 implementations of any needed algorithms when available.
360 ESP can be used with various encryption and authentication algorithms.
362 implementations of the algorithms that RFC 8221 lists as MUST be
363 implemented. If you need any other algorithms, you'll need to enable
365 implementations of any needed algorithms when available.
|
| /linux/Documentation/locking/ |
| H A D | pi-futex.rst | 33 technique that often cannot be replaced with lockless algorithms. As we
38 algorithms often endangers to ability to do robust reviews of said code.
40 data structures, instead of lockless algorithms. Furthermore, there are
|
| /linux/Documentation/userspace-api/media/ |
| H A D | glossary.rst | 110 A specialized processor that implements a set of algorithms for
111 processing image data. ISPs may implement algorithms for lens
114 algorithms (e.g. automatic exposure, white balance and focus).
|
| /linux/fs/verity/ |
| H A D | hash_algs.c | 3 * fs-verity hash algorithms
10 /* The hash algorithms supported by fs-verity */
157 * Sanity check the hash algorithms (could be a build-time check, but in fsverity_check_hash_algs()
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-block-zram | 30 available and selected compression algorithms, change
138 or show secondary compression algorithms.
145 with secondary compression algorithms.
|
| H A D | sysfs-driver-uacce | 40 What: /sys/class/uacce/<dev_name>/algorithms
44 Description: Algorithms supported by this accelerator, separated by new line.
|
| /linux/Documentation/driver-api/crypto/iaa/ |
| H A D | iaa-crypto.rst | 21 one of the supported IAA compression algorithms in whatever facility
22 allows compression algorithms to be selected.
211 As a result, the IAA crypto algorithms and thus the IAA hardware are
216 algorithms can be unregistered by removing the module.
228 The attribute settings at the time the IAA algorithms are registered
615 algorithms are enabled and available. When the IAA crypto algorithms
659 In order to unregister the IAA crypto algorithms, and register new
713 will unregister the current IAA crypto algorithms::
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | intel_uncore_frequency_scaling.rst | 17 performance, SoCs have internal algorithms for scaling uncore frequency. These
18 algorithms monitor workload usage of uncore and set a desirable frequency.
131 per watt. With this feature hardware power management algorithms
|
| /linux/drivers/crypto/qce/ |
| H A D | common.h | 35 /* cipher algorithms */
40 /* hash and hmac algorithms */
|
| /linux/fs/f2fs/ |
| H A D | Kconfig | 27 layout, but also for selecting allocation and cleaning algorithms.
100 multiple back-end compression algorithms are supported.
|
| /linux/include/uapi/linux/ |
| H A D | pfkeyv2.h | 303 /* Authentication algorithms */
316 /* Encryption algorithms */
339 /* Compression algorithms */
|
| /linux/drivers/crypto/caam/ |
| H A D | caamhash_desc.c | 3 * Shared descriptors for ahash algorithms
80 * hash algorithms
|
| /linux/drivers/crypto/cavium/nitrox/ |
| H A D | nitrox_sriov.c | 85 /* unregister crypto algorithms */ in nitrox_pf_cleanup()
122 /* register crypto algorithms */ in nitrox_pf_reinit()
|
| /linux/drivers/crypto/ |
| H A D | sa2ul.h | 343 /* Encryption algorithms */
358 /* Authentication algorithms */
378 * Mode control engine algorithms used to index the
|
| /linux/net/batman-adv/ |
| H A D | bat_algo.c | 75 /* all algorithms must implement all ops (for now) */ in batadv_algo_register()
183 * algorithms
|