| /linux/lib/crypto/ |
| H A D | Kconfig | 38 This symbol can be depended upon by arch implementations of the
40 fallback, e.g., for SIMD implementations. If no arch specific
56 This symbol can be selected by arch implementations of the ChaCha
58 for SIMD implementations. If no arch specific implementation is
79 This symbol can be depended upon by arch implementations of the
81 fallback, e.g., for SIMD implementations. If no arch specific
119 This symbol can be selected by arch implementations of the Poly1305
121 for SIMD implementations. If no arch specific implementation is
165 This symbol can be selected by arch implementations of the SHA-256
167 for SIMD implementations
[all...] |
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-log.rst | 15 implementations use to perform logging operations (see
17 logging implementations are available and provide different
43 so log implementations can be done there. This is done by forwarding most
53 There are currently two userspace log implementations that leverage this
54 framework - "clustered-disk" and "clustered-core". These implementations
56 can be used in a shared-storage environment when the cluster log implementations
|
| /linux/fs/crypto/ |
| H A D | Kconfig | 26 # Also note that this option only pulls in the generic implementations of the
27 # algorithms, not any per-architecture optimized implementations. It is
28 # strongly recommended to enable optimized implementations too.
|
| /linux/Documentation/bpf/ |
| H A D | bpf_licensing.rst | 26 Implementations of eBPF
35 The reference implementations of the eBPF interpreter and various just-in-time
43 There are also implementations of eBPF runtime (interpreter, JITs, helper
58 Other kernels or user space implementations of eBPF instruction set and runtime
|
| /linux/Documentation/netlabel/ |
| H A D | draft-ietf-cipso-ipsecurity-01.txt | 117 not appear as the DOI identifier in any CIPSO option. Implementations
150 identifier field in the CIPSO header, implementations should assume that
160 types, implementations will require the DOI identifier as well as the tag
163 interoperability with other networks will not be an issue. Implementations
237 speed many implementations including router implementations.
334 speed many implementations including router implementations.
386 speed many implementations including router implementations.
447 parameters are required for CIPSO implementations:
543 CIPSO implementations that support only one label are not required to
544 support the parameters described above. These limited implementations are
|
| /linux/drivers/net/ethernet/ibm/emac/ |
| H A D | emac.h | 28 /* Common registers across all EMAC implementations. */
42 /* Registers unique to EMAC4 implementations */
53 /* Registers unique to EMAC4SYNC implementations */
62 /* Common registers across all EMAC implementations. */
72 /* Registers unique to EMAC4 implementations */
76 /* Registers unique to EMAC4SYNC implementations */
|
| /linux/Documentation/core-api/ |
| H A D | genericirq.rst | 67 Analysing a couple of architecture's IRQ subsystem implementations
75 which is normally one of the generic implementations. (This high-level
86 of existing implementations, the __do_IRQ() super-handler is still
177 Default flow implementations
184 default flow implementations. The following helper functions are
219 Default flow handler implementations
349 implementations.
392 To avoid copies of identical implementations of IRQ chips the core
|
| /linux/mm/ |
| H A D | zpool.c | 7 * This is a common frontend for memory storage pool implementations.
141 * Implementations must guarantee this to be thread-safe.
192 * Implementations must guarantee this to be thread-safe,
214 * Implementations must guarantee this to be thread-safe.
237 * Implementations must guarantee this to be thread-safe.
256 * Implementations must guarantee this to be thread-safe,
|
| /linux/Documentation/crypto/ |
| H A D | intro.rst | 27 - data transformation implementations (typically ciphers) that can be
33 implementations (i.e. implementations of ciphers and other
|
| /linux/Documentation/nvme/ |
| H A D | feature-and-quirk-policy.rst | 62 Sometimes implementations of open standards fail to correctly implement parts
66 Typically these implementations are not or only superficially tested with Linux
69 The Linux NVMe maintainers decide ad hoc whether to quirk implementations
|
| /linux/drivers/crypto/caam/ |
| H A D | Kconfig | 97 bool "Register algorithm implementations with the Crypto API"
128 bool "Register hash algorithm implementations with Crypto API"
137 bool "Register public key cryptography implementations with Crypto API"
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | psci.yaml | 41 For implementations complying to PSCI versions prior to 0.2.
45 For implementations complying to PSCI 0.2.
56 For implementations complying to PSCI 1.0.
120 helps to implement support for OSI mode and OS implementations may choose
|
| /linux/net/ipv6/ |
| H A D | Kconfig | 59 implementations of the algorithms that RFC 8221 lists as MUST be
62 implementations of any needed algorithms when available.
74 implementations of the algorithms that RFC 8221 lists as MUST be
77 implementations of any needed algorithms when available.
|
| /linux/Documentation/admin-guide/ |
| H A D | ufs.rst | 13 The problem are differences among implementations. Features of
14 some implementations are undocumented, so its hard to recognize
|
| /linux/arch/openrisc/include/asm/ |
| H A D | cmpxchg.h | 2 * 1,2 and 4 byte cmpxchg and xchg implementations for OpenRISC.
12 * The portable implementations of 1 and 2 byte xchg and cmpxchg using a 4
13 * byte cmpxchg is sourced heavily from the sh and mips implementations.
|
| /linux/Documentation/devicetree/bindings/firmware/xilinx/ |
| H A D | xlnx,zynqmp-firmware.yaml | 23 - description: For implementations complying for Zynq Ultrascale+ MPSoC.
26 - description: For implementations complying for Versal.
29 - description: For implementations complying for Versal NET.
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | rkisp1.rst | 9 The rkisp1 block underwent some changes between SoC implementations.
18 Right now the kernel supports rkisp1 implementations based
|
| /linux/drivers/pci/hotplug/ |
| H A D | TODO | 5 * There are no implementations of the ->hardware_test, ->get_power and
25 * Implementations of hotplug_slot_ops callbacks such as get_adapter_present()
|
| /linux/arch/arm/include/debug/ |
| H A D | samsung.S | 10 /* The S5PV210/S5PC110 implementations are as belows. */
24 /* The S3C2440 implementations are used by default as they are the
|
| /linux/lib/raid6/ |
| H A D | neon.c | 20 * from the actual implementations in neonN.c (generated from neon.uc by
22 * - the actual implementations use NEON intrinsics, and the GCC support header
|
| /linux/Documentation/sound/designs/ |
| H A D | tracepoints.rst | 93 it. Else, zero. But this behaviour depends on implementations in driver
99 it. Else, zero. But this behaviour depends on implementations in driver
106 on implementations in driver side.
|
| /linux/Documentation/watchdog/ |
| H A D | mlx-wdt.rst | 13 There are 2 types of HW watchdog implementations.
54 This mlx-wdt driver supports both HW watchdog implementations.
|
| /linux/arch/arm/include/asm/ |
| H A D | outercache.h | 75 * It is intended that this function is only used by implementations
77 * (Some implementations perform this as a clean followed by an invalidate.)
|
| /linux/Documentation/driver-api/soundwire/ |
| H A D | error_handling.rst | 36 signals the command was ignored. Some Master implementations allow for a
39 solution. Alternatively some implementations might directly issue a bus
|
| /linux/Documentation/infiniband/ |
| H A D | tag_matching.rst | 25 Implementations frequently use different matching schemes for these two
28 To keep MPI library memory footprint down, MPI implementations typically use
|