Home
last modified time | relevance | path

Searched full:implementation (Results 1 – 25 of 3155) sorted by relevance

12345678910>>...127

/Linux-v5.10/lib/crypto/
DKconfig15 accelerated implementation of the Blake2s library interface,
24 implementation is enabled, this implementation serves the users
33 by either the generic implementation or an arch-specific one, if one
40 accelerated implementation of the ChaCha library interface,
50 implementation is enabled, this implementation serves the users
59 by either the generic implementation or an arch-specific one, if one
66 accelerated implementation of the Curve25519 library interface,
75 implementation is enabled, this implementation serves the users
84 fulfilled by either the generic implementation or an arch-specific
101 accelerated implementation of the Poly1305 library interface,
[all …]
Dcurve25519-generic.c5 * This is an implementation of the Curve25519 ECDH algorithm, using either
6 * a 32-bit implementation or a 64-bit implementation with 128-bit integers,
Dcurve25519.c5 * This is an implementation of the Curve25519 ECDH algorithm, using either
6 * a 32-bit implementation or a 64-bit implementation with 128-bit integers,
/Linux-v5.10/Documentation/crypto/
Darchitecture.rst103 the following implementations: AES-NI, assembler implementation, or
105 which cipher implementation is used? The answer to that question is the
106 priority number assigned to each cipher implementation by the kernel
109 implementations providing an implementation with that name and selects
110 the implementation with the highest priority.
113 implementation and thus does not want to rely on the priority-based
115 the cipher implementation to register a unique name in addition to
117 sure to refer to the intended cipher implementation.
133 - module: the kernel module providing the cipher implementation (or
136 - priority: the priority value of the cipher implementation
[all …]
Dintro.rst43 The transformation implementation is an actual code or interface to
48 implementation. There can be multiple transformation objects associated
49 with a single transformation implementation. Each of those
52 consumer requests a transformation implementation. The consumer is then
/Linux-v5.10/drivers/mailbox/
DKconfig23 Mailbox implementation for i.MX Messaging Unit (MU).
39 An implementation of the ARM PL320 Interprocessor Communication
50 Mailbox implementation for communication with the the firmware
59 Mailbox implementation for OMAP family chips with hardware for
98 An implementation of the Altera Mailbox soft core. It is used
106 An implementation of the BCM2385 Mailbox. It is used to invoke
114 Mailbox implementation for STMicroelectonics family chips with
121 An implementation of Message Manager slave driver for Keystone
134 An implementation of the hi3660 mailbox. It is used to send message
144 An implementation of the hi6220 mailbox. It is used to send message
[all …]
/Linux-v5.10/Documentation/arm/samsung/
Dgpio.rst2 Samsung GPIO implementation
8 This outlines the Samsung GPIO implementation and the architecture
16 about these devices. Their implementation has been brought into line
17 with the core samsung implementation described in this document.
23 The gpio implementation uses gpiolib as much as possible, only providing
35 implementation to configure pins as necessary.
/Linux-v5.10/arch/arm/crypto/
DKconfig73 fastest AES implementation for single blocks. For multiple
74 blocks, the NEON bit-sliced implementation is usually faster.
76 This implementation may be vulnerable to cache timing attacks,
88 Use a faster and more secure NEON based implementation of AES in CBC,
94 This implementation does not rely on any lookup tables so it is
104 Use an implementation of AES in CBC, CTR and XTS modes that uses
114 Use an implementation of GHASH (used by the GCM AEAD chaining mode)
/Linux-v5.10/Documentation/core-api/
Dgenericirq.rst28 The original implementation of interrupt handling in Linux uses the
33 a quite universal set for the ARM interrupt handler implementation in
42 During the implementation we identified another type:
51 This split implementation of high-level IRQ handlers allows us to
56 The original general IRQ implementation used hw_interrupt_type
76 flow handler implementation also makes it simple to provide
82 IRQ-flow implementation for 'level type' interrupts and add a
83 (sub)architecture specific 'edge type' implementation.
225 handle_level_irq provides a generic implementation for level-triggered
238 handle_fasteoi_irq provides a generic implementation for interrupts,
[all …]
/Linux-v5.10/Documentation/networking/
Dx25.rst8 write an X.25 implementation for Linux. My aim is to provide a complete X.25
15 I therefore decided to write the implementation such that as far as the
18 implementation of LAPB. Therefore the LAPB modules would be called by
22 To confuse matters a little, an 802.2 LLC implementation for Linux is being
27 implementation is being done as part of another protocol project (SNA) and
/Linux-v5.10/drivers/char/xilinx_hwicap/
Dbuffer_icap.h13 * OR INFORMATION AS ONE POSSIBLE IMPLEMENTATION OF THIS FEATURE,
15 * THAT THIS IMPLEMENTATION IS FREE FROM ANY CLAIMS OF INFRINGEMENT,
17 * FOR YOUR IMPLEMENTATION. XILINX EXPRESSLY DISCLAIMS ANY
19 * IMPLEMENTATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR
20 * REPRESENTATIONS THAT THIS IMPLEMENTATION IS FREE FROM CLAIMS OF
Dfifo_icap.h13 * OR INFORMATION AS ONE POSSIBLE IMPLEMENTATION OF THIS FEATURE,
15 * THAT THIS IMPLEMENTATION IS FREE FROM ANY CLAIMS OF INFRINGEMENT,
17 * FOR YOUR IMPLEMENTATION. XILINX EXPRESSLY DISCLAIMS ANY
19 * IMPLEMENTATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OR
20 * REPRESENTATIONS THAT THIS IMPLEMENTATION IS FREE FROM CLAIMS OF
/Linux-v5.10/Documentation/networking/caif/
Dlinux_caif.rst29 The implementation of CAIF is divided into:
32 * CAIF Core Protocol Implementation
59 Implementation chapter
75 The Core CAIF implementation contains:
77 - Simple implementation of CAIF.
92 Implementation. The support functions include:
94 - CFPKT CAIF Packet. Implementation of CAIF Protocol Packet. The
98 The CAIF Protocol implementation contains:
/Linux-v5.10/security/selinux/
Dxfrm.c150 * LSM hook implementation that authorizes that a flow can use a xfrm policy
173 * LSM hook implementation that authorizes that a state matches
258 * LSM hook implementation that checks and/or returns the xfrm sid for the
282 * LSM hook implementation that allocs and transfers uctx spec to xfrm_policy.
292 * LSM hook implementation that copies security data structure from old to new
314 * LSM hook implementation that frees xfrm_sec_ctx security information.
322 * LSM hook implementation that authorizes deletion of labeled policies.
330 * LSM hook implementation that allocates a xfrm_sec_state, populates it using
340 * LSM hook implementation that allocates a xfrm_sec_state and populates based
382 * LSM hook implementation that frees xfrm_state security information.
[all …]
/Linux-v5.10/arch/openrisc/
DKconfig87 Select this if your implementation features write through data caches.
104 Select this if your implementation has the Class II instruction l.ff1
110 Select this if your implementation has the Class II instruction l.fl1
116 Select this if your implementation has a hardware multiply instruction
122 Select this if your implementation has a hardware divide instruction
/Linux-v5.10/Documentation/driver-api/
Dmen-chameleon-bus.rst9 1.2 Limitations of the current implementation
26 This document describes the architecture and implementation of the MEN
33 implementation and does by no means describe the complete possibilities of MCB
36 Limitations of the current implementation
39 The current implementation is limited to PCI and PCIe based carrier devices
68 not handled by the MCB implementation.
97 The current implementation assigns exactly one memory and one IRQ resource
/Linux-v5.10/Documentation/locking/
Dfutex-requeue-pi.rst16 Without requeue_pi, the glibc implementation of
20 implementation would wake the highest-priority waiter, and leave the
56 user space already holding the PI futex. The glibc implementation
81 The actual glibc implementation will likely test for PI and make the
86 Implementation section in Futex Requeue PI
106 to be requeued to a PI-aware futex. The implementation is the
/Linux-v5.10/net/ipv4/
Dtcp_lp.c11 * the original TCP-LP implementation:
27 * Original implementation for 2.4.19:
74 * We get the idea from original TCP-LP implementation where only left those we
94 * Clone the handling from Vegas module implementation.
115 * Implementation of cong_avoid.
132 * implementation only guest it for once and use forever.
214 * Implementation or rtt_sample.
219 * Most ideas come from the original TCP-LP implementation.
258 * Implementation of pkts_acked.
/Linux-v5.10/drivers/gpu/drm/amd/amdgpu/
Damdgpu_dma_buf.c45 * amdgpu_gem_prime_vmap - &dma_buf_ops.vmap implementation
67 * amdgpu_gem_prime_vunmap - &dma_buf_ops.vunmap implementation
81 * amdgpu_gem_prime_mmap - &drm_driver.gem_prime_mmap implementation
169 * amdgpu_dma_buf_attach - &dma_buf_ops.attach implementation
212 * amdgpu_dma_buf_detach - &dma_buf_ops.detach implementation
231 * amdgpu_dma_buf_pin - &dma_buf_ops.pin implementation
247 * amdgpu_dma_buf_unpin - &dma_buf_ops.unpin implementation
262 * amdgpu_dma_buf_map - &dma_buf_ops.map_dma_buf implementation
336 * amdgpu_dma_buf_unmap - &dma_buf_ops.unmap_dma_buf implementation
363 * amdgpu_dma_buf_begin_cpu_access - &dma_buf_ops.begin_cpu_access implementation
[all …]
/Linux-v5.10/tools/perf/include/bpf/linux/
Dsocket.h8 #define _K_SS_MAXSIZE 128 /* Implementation specific max size */
10 /* Implementation specific desired alignment */
16 /* Following field(s) are implementation specific */
/Linux-v5.10/include/uapi/linux/
Dsocket.h8 #define _K_SS_MAXSIZE 128 /* Implementation specific max size */
20 /* Following field(s) are implementation specific */
25 void *__align; /* implementation specific desired alignment */
/Linux-v5.10/kernel/rcu/
DKconfig12 This option selects the RCU implementation that is
22 This option selects the RCU implementation that is
34 This option selects the RCU implementation that is
83 This option enables a task-based RCU implementation that uses
90 This option enables a task-based RCU implementation that uses
99 This option enables a task-based RCU implementation that uses
129 systems, but if you are stress-testing the RCU implementation
/Linux-v5.10/drivers/net/ethernet/mellanox/mlxsw/
DKconfig33 tristate "PCI bus implementation for Mellanox Technologies Switch ASICs"
37 This is PCI bus implementation for Mellanox Technologies Switch ASICs.
43 tristate "I2C bus implementation for Mellanox Technologies Switch ASICs"
47 This is I2C bus implementation for Mellanox Technologies Switch ASICs.
/Linux-v5.10/crypto/
DKconfig230 Generic implementation of the RSA public key algorithm.
237 Generic implementation of the Diffie-Hellman algorithm.
248 Generic implementation of the ECDH algorithm
271 Generic implementation of the SM2 public key algorithm. It was
339 tristate "AEGIS-128 AEAD algorithm (x86_64 AESNI+SSE2 implementation)"
344 AESNI+SSE2 implementation of the AEGIS-128 dedicated AEAD algorithm.
457 key size 256, 384 or 512 bits. This implementation currently
474 tristate "NHPoly1305 hash function (x86_64 SSE2 implementation)"
478 SSE2 optimized implementation of the hash function used by the
482 tristate "NHPoly1305 hash function (x86_64 AVX2 implementation)"
[all …]
/Linux-v5.10/mm/
Dzpool.c37 * zpool_register_driver() - register a zpool implementation.
50 * zpool_unregister_driver() - unregister a zpool implementation.
146 * used when allocating memory, if the implementation supports it. If the
266 * implementation supports it. The provided @handle will be
329 * param indicates to the implementation how the memory will be
331 * implementation does not support it, the memory will be treated
338 * as soon as possible. As the implementation may use per-cpu
356 * actions that the implementation took in zpool_map_handle()
386 * in its implementation of zpool_driver.shrink. It could do internal

12345678910>>...127