Searched full:implementations (Results 1 – 25 of 198) sorted by relevance
12345678
| /Documentation/admin-guide/device-mapper/ |
| 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
|
| /Documentation/bpf/ |
| 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
|
| /Documentation/crypto/ |
| D | intro.rst | 27 - data transformation implementations (typically ciphers) that can be
33 implementations (i.e. implementations of ciphers and other
|
| D | architecture.rst | 23 The kernel crypto API provides implementations of single block ciphers
101 The kernel crypto API may provide multiple implementations of a template
103 the following implementations: AES-NI, assembler implementation, or
109 implementations providing an implementation with that name and selects
243 existing cipher implementations. The first section addresses the most
258 generic C implementations (gcm.c, aes-generic.c, ctr.c, ghash-generic.c,
262 It is possible that some streamlined cipher implementations (like
263 AES-NI) provide implementations merging aspects which in the view of the
374 Keyed message digest implementations again follow the same concept as
|
| D | index.rst | 9 concepts, details about developing cipher implementations, employment of the API
|
| /Documentation/admin-guide/ |
| D | ufs.rst | 13 The problem are differences among implementations. Features of
14 some implementations are undocumented, so its hard to recognize
|
| /Documentation/nvme/ |
| 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
|
| /Documentation/devicetree/bindings/mfd/ |
| D | google,cros-ec.yaml | 23 For implementations of the EC connected through I2C.
26 For implementations of the EC connected through SPI.
29 For implementations of the FPMCU connected through SPI.
34 For implementations of the EC connected through RPMSG.
37 For implementations of the EC connected through UART.
57 Some implementations of the EC include a small nvram space used to
|
| /Documentation/filesystems/ |
| D | index.rst | 49 filesystem implementations.
63 Documentation for filesystem implementations.
|
| /Documentation/driver-api/media/drivers/ |
| D | rkisp1.rst | 9 The rkisp1 block underwent some changes between SoC implementations.
18 Right now the kernel supports rkisp1 implementations based
|
| /Documentation/core-api/ |
| 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
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-chromeos-driver-cros-ec-vbc | 6 small nvram space on some EC implementations.
|
| /Documentation/netlabel/ |
| 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
|
| /Documentation/sound/designs/ |
| D | index.rst | 1 Designs and Implementations
|
| 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.
|
| /Documentation/watchdog/ |
| D | mlx-wdt.rst | 13 There are 2 types of HW watchdog implementations.
54 This mlx-wdt driver supports both HW watchdog implementations.
|
| /Documentation/devicetree/bindings/arm/ |
| 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
|
| /Documentation/devicetree/bindings/firmware/xilinx/ |
| 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.
|
| /Documentation/driver-api/soundwire/ |
| 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
|
| /Documentation/infiniband/ |
| 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
|
| /Documentation/arch/mips/ |
| D | booting.rst | 28 currently any 64-bit BMIPS implementations.
|
| /Documentation/devicetree/bindings/mtd/ |
| D | raw-nand-chip.yaml | 22 not all implementations must support all possible
23 combinations. However, implementations are encouraged to further
|
| /Documentation/arch/arm/nwfpe/ |
| D | todo.rst | 63 implementations: it is there to control the hardware in an implementation-
66 reserved to alter it between implementations) and the WFC and RFC
|
| /Documentation/devicetree/bindings/i3c/ |
| D | mipi-i3c-hci.yaml | 20 host controller hardware implementations from multiple vendors.
|
| /Documentation/devicetree/bindings/arm/firmware/ |
| D | sdei.txt | 28 * "arm,sdei-1.0" : For implementations complying to SDEI version 1.x.
|
12345678