| /kernel/linux/linux-5.10/Documentation/block/ |
| D | null_blk.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Null block device driver
10 The null block device (``/dev/nullb*``) is used for benchmarking the various
11 block-layer implementations. It emulates a block device of X gigabytes in size.
15 Multi-queue block-layer
17 - Request-based.
18 - Configurable submission queues per device.
20 No block-layer (Known as bio-based)
22 - Bio-based. IO requests are submitted directly to the device driver.
23 - Directly accepts bio data structure and returns them.
[all …]
|
| D | blk-mq.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Multi-Queue Block IO Queueing Mechanism (blk-mq)
7 The Multi-Queue Block IO Queueing Mechanism is an API to enable fast storage
9 through queueing and submitting IO requests to block devices simultaneously,
16 ----------
19 development of the kernel. The Block IO subsystem aimed to achieve the best
26 However, with the development of Solid State Drives and Non-Volatile Memories
30 in those devices' design, the multi-queue mechanism was introduced.
32 The former design had a single queue to store block IO requests with a single
36 to different CPUs) wanted to perform block IO. Instead of this, the blk-mq API
[all …]
|
| D | biodoc.rst | 2 Notes on the Generic Block Layer Rewrite in Linux 2.5
13 - Jens Axboe <jens.axboe@oracle.com>
14 - Suparna Bhattacharya <suparna@in.ibm.com>
19 - Nick Piggin <npiggin@kernel.dk>
24 These are some notes describing some aspects of the 2.5 block layer in the
34 - Jens Axboe <jens.axboe@oracle.com>
36 Many aspects of the generic block layer redesign were driven by and evolved
43 - Christoph Hellwig <hch@infradead.org>
44 - Arjan van de Ven <arjanv@redhat.com>
45 - Randy Dunlap <rdunlap@xenotime.net>
[all …]
|
| /kernel/linux/linux-6.6/Documentation/block/ |
| D | null_blk.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Null block device driver
10 The null block device (``/dev/nullb*``) is used for benchmarking the various
11 block-layer implementations. It emulates a block device of X gigabytes in size.
15 Multi-queue block-layer
17 - Request-based.
18 - Configurable submission queues per device.
20 No block-layer (Known as bio-based)
22 - Bio-based. IO requests are submitted directly to the device driver.
23 - Directly accepts bio data structure and returns them.
[all …]
|
| D | blk-mq.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Multi-Queue Block IO Queueing Mechanism (blk-mq)
7 The Multi-Queue Block IO Queueing Mechanism is an API to enable fast storage
9 through queueing and submitting IO requests to block devices simultaneously,
16 ----------
19 development of the kernel. The Block IO subsystem aimed to achieve the best
26 However, with the development of Solid State Drives and Non-Volatile Memories
30 in those devices' design, the multi-queue mechanism was introduced.
32 The former design had a single queue to store block IO requests with a single
36 to different CPUs) wanted to perform block IO. Instead of this, the blk-mq API
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/mellanox/mlxfw/ |
| D | mlxfw_mfa2.c | 1 // SPDX-License-Identifier: BSD-3-Clause OR GPL-2.0
2 /* Copyright (c) 2017-2019 Mellanox Technologies. All rights reserved */
18 * +----------------------------------+
20 * +----------------------------------+
22 * | +------------------------------+ | +-----------------+
23 * | | package descriptor tlv +-----> |num_devices=n |
24 * | +------------------------------+ | |num_components=m |
25 * +----------------------------------+ |CB offset |
27 * | +------------------------------+ | | |
28 * | | PSID tlv | | +-----------------+
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/mellanox/mlxfw/ |
| D | mlxfw_mfa2.c | 1 // SPDX-License-Identifier: BSD-3-Clause OR GPL-2.0
2 /* Copyright (c) 2017-2019 Mellanox Technologies. All rights reserved */
18 * +----------------------------------+
20 * +----------------------------------+
22 * | +------------------------------+ | +-----------------+
23 * | | package descriptor tlv +-----> |num_devices=n |
24 * | +------------------------------+ | |num_components=m |
25 * +----------------------------------+ |CB offset |
27 * | +------------------------------+ | | |
28 * | | PSID tlv | | +-----------------+
[all …]
|
| /kernel/linux/linux-5.10/include/xen/interface/io/ |
| D | blkif.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
5 * Unified block-device I/O interface for Xen guest OSes.
7 * Copyright (c) 2003-2004, Keir Fraser
17 * Front->back notifications: When enqueuing a new request, sending a
19 * hold-off mechanism provided by the ring macros). Backends must set
22 * Back->front notifications: When enqueuing a new response, sending a
24 * hold-off mechanism provided by the ring macros). Frontends must set
33 * If supported, the backend will write the key "multi-queue-max-queues" to
37 * key "multi-queue-num-queues" with the number they wish to use, which must be
39 * "multi-queue-max-queues".
[all …]
|
| /kernel/linux/linux-6.6/include/xen/interface/io/ |
| D | blkif.h | 1 /* SPDX-License-Identifier: MIT */
5 * Unified block-device I/O interface for Xen guest OSes.
7 * Copyright (c) 2003-2004, Keir Fraser
17 * Front->back notifications: When enqueuing a new request, sending a
19 * hold-off mechanism provided by the ring macros). Backends must set
22 * Back->front notifications: When enqueuing a new response, sending a
24 * hold-off mechanism provided by the ring macros). Frontends must set
33 * If supported, the backend will write the key "multi-queue-max-queues" to
37 * key "multi-queue-num-queues" with the number they wish to use, which must be
39 * "multi-queue-max-queues".
[all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ext4/ |
| D | allocators.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 Block and Inode Allocation Policy
4 ---------------------------------
9 that the head actuator and disk must perform to access a data block,
13 effect of concentrating writes on a single erase block, which can speed
17 The first tool that ext4 uses to combat fragmentation is the multi-block
18 allocator. When a file is first created, the block allocator
23 files) then the file data gets written out in a single multi-block
33 file's data blocks in the same block group as its inode. This cuts down
39 same block group as the directory, when feasible. The working assumption
[all …]
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ext4/ |
| D | allocators.rst | 1 .. SPDX-License-Identifier: GPL-2.0
3 Block and Inode Allocation Policy
4 ---------------------------------
9 that the head actuator and disk must perform to access a data block,
13 effect of concentrating writes on a single erase block, which can speed
17 The first tool that ext4 uses to combat fragmentation is the multi-block
18 allocator. When a file is first created, the block allocator
23 files) then the file data gets written out in a single multi-block
33 file's data blocks in the same block group as its inode. This cuts down
39 same block group as the directory, when feasible. The working assumption
[all …]
|
| /kernel/linux/linux-5.10/Documentation/crypto/ |
| D | devel-algos.rst | 5 --------------------------------------------
14 filled with each, struct crypto_alg, must be considered -- see below
47 Single-Block Symmetric Ciphers [CIPHER]
48 ---------------------------------------
55 block at a time and there are no dependencies between blocks at all.
69 Struct cipher_alg defines a single block cipher.
74 during any of these are in-flight.
78 KEY ---. PLAINTEXT ---.
80 .cia_setkey() -> .cia_encrypt()
82 '-----> CIPHERTEXT
[all …]
|
| /kernel/linux/linux-6.6/Documentation/crypto/ |
| D | devel-algos.rst | 5 --------------------------------------------
14 filled with each, struct crypto_alg, must be considered -- see below
47 Single-Block Symmetric Ciphers [CIPHER]
48 ---------------------------------------
55 block at a time and there are no dependencies between blocks at all.
69 Struct cipher_alg defines a single block cipher.
74 during any of these are in-flight.
78 KEY ---. PLAINTEXT ---.
80 .cia_setkey() -> .cia_encrypt()
82 '-----> CIPHERTEXT
[all …]
|
| /kernel/linux/linux-6.6/drivers/staging/media/atomisp/pci/isp/kernels/macc/macc1_5/ |
| D | ia_css_macc1_5_types.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
20 * CSS-API header file for Multi-Axis Color Conversion algorithm parameters.
23 /* Multi-Axis Color Conversion configuration
33 /* Multi-Axes Color Correction (MACC) table.
35 * ISP block: MACC (MACC by only matrix)
49 * OutU = (data00 * InU + data01 * InV) >> (13 - exp)
50 * OutV = (data10 * InU + data11 * InV) >> (13 - exp)
53 * OutU = (4096 * InU + 0 * InV) >> (13 - 1)
54 * OutV = ( 0 * InU + 4096 * InV) >> (13 - 1)
59 MACC1_5: s[macc_config.exp].[13-macc_config.exp], [-8192,8191]
[all …]
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/isp/kernels/macc/macc1_5/ |
| D | ia_css_macc1_5_types.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
20 * CSS-API header file for Multi-Axis Color Conversion algorithm parameters.
23 /* Multi-Axis Color Conversion configuration
33 /* Multi-Axes Color Correction (MACC) table.
35 * ISP block: MACC (MACC by only matrix)
49 * OutU = (data00 * InU + data01 * InV) >> (13 - exp)
50 * OutV = (data10 * InU + data11 * InV) >> (13 - exp)
53 * OutU = (4096 * InU + 0 * InV) >> (13 - 1)
54 * OutV = ( 0 * InU + 4096 * InV) >> (13 - 1)
59 MACC1_5: s[macc_config.exp].[13-macc_config.exp], [-8192,8191]
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/netlink/ |
| D | genetlink-legacy.rst | 1 .. SPDX-License-Identifier: BSD-3-Clause
9 the ``genetlink-legacy`` protocol level.
15 --------------------
17 New Netlink families should use ``multi-attr`` to define arrays.
21 For reference the ``multi-attr`` array may look like this::
23 [ARRAY-ATTR]
27 [SOME-OTHER-ATTR]
28 [ARRAY-ATTR]
33 where ``ARRAY-ATTR`` is the array entry type.
35 array-nest
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/dma/ |
| D | snps,dma-spear1340.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/dma/snps,dma-spear1340.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <vireshk@kernel.org>
11 - Andy Shevchenko <andriy.shevchenko@linux.intel.com>
14 - $ref: dma-controller.yaml#
19 - const: snps,dma-spear1340
20 - items:
21 - enum:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/dma/ |
| D | snps,dma-spear1340.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/dma/snps,dma-spear1340.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <vireshk@kernel.org>
11 - Andy Shevchenko <andriy.shevchenko@linux.intel.com>
14 - $ref: "dma-controller.yaml#"
18 const: snps,dma-spear1340
20 "#dma-cells":
40 clock-names:
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | samsung,sec-core.txt | 1 Binding for Samsung S2M and S5M family multi-function device
4 This is a part of device tree bindings for S2M and S5M family multi-function
8 of multi-function devices which include voltage and current regulators, RTC,
9 charger controller, clock outputs and other sub-blocks. It is interfaced
10 to the host controller using an I2C interface. Each sub-block is usually
14 This document describes bindings for main device node. Optional sub-blocks
15 must be a sub-nodes to it. Bindings for them can be found in:
16 - bindings/regulator/samsung,s2mpa01.txt
17 - bindings/regulator/samsung,s2mps11.txt
18 - bindings/regulator/samsung,s5m8767.txt
[all …]
|
| D | brcm,iproc-mhb.txt | 1 Broadcom iProc Multi Host Bridge (MHB)
3 Certain Broadcom iProc SoCs have a multi host bridge (MHB) block that controls
10 - compatible: should contain:
11 "brcm,sr-mhb", "syscon" for Stingray
12 - reg: base address and range of the MHB registers
16 compatible = "brcm,sr-mhb", "syscon";
|
| /kernel/linux/linux-5.10/Documentation/driver-api/media/drivers/ |
| D | tuners.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ------------------------
12 - L= LG_API (VHF_LO=0x01, VHF_HI=0x02, UHF=0x08, radio=0x04)
13 - P= PHILIPS_API (VHF_LO=0xA0, VHF_HI=0x90, UHF=0x30, radio=0x04)
14 - T= TEMIC_API (VHF_LO=0x02, VHF_HI=0x04, UHF=0x01)
15 - A= ALPS_API (VHF_LO=0x14, VHF_HI=0x12, UHF=0x11)
16 - M= PHILIPS_MK3 (VHF_LO=0x01, VHF_HI=0x02, UHF=0x04, radio=0x19)
19 -------------------
21 - Samsung Tuner identification: (e.g. TCPM9091PD27)
23 .. code-block:: none
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/media/drivers/ |
| D | tuners.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 ------------------------
12 - L= LG_API (VHF_LO=0x01, VHF_HI=0x02, UHF=0x08, radio=0x04)
13 - P= PHILIPS_API (VHF_LO=0xA0, VHF_HI=0x90, UHF=0x30, radio=0x04)
14 - T= TEMIC_API (VHF_LO=0x02, VHF_HI=0x04, UHF=0x01)
15 - A= ALPS_API (VHF_LO=0x14, VHF_HI=0x12, UHF=0x11)
16 - M= PHILIPS_MK3 (VHF_LO=0x01, VHF_HI=0x02, UHF=0x04, radio=0x19)
19 -------------------
21 - Samsung Tuner identification: (e.g. TCPM9091PD27)
23 .. code-block:: none
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | brcm,iproc-mhb.txt | 1 Broadcom iProc Multi Host Bridge (MHB)
3 Certain Broadcom iProc SoCs have a multi host bridge (MHB) block that controls
10 - compatible: should contain:
11 "brcm,sr-mhb", "syscon" for Stingray
12 - reg: base address and range of the MHB registers
16 compatible = "brcm,sr-mhb", "syscon";
|
| /kernel/linux/linux-5.10/sound/pci/ctxfi/ |
| D | ctresource.c | 1 // SPDX-License-Identifier: GPL-2.0-only
21 /* Resource allocation based on bit-map management mechanism */
24 unsigned int multi, unsigned int *ridx) in get_resource() argument
29 for (i = 0, n = multi; i < amount; i++) { in get_resource()
33 n = multi; in get_resource()
36 if (!(--n)) in get_resource()
42 return -ENOENT; in get_resource()
45 /* Mark the contiguous bits in resource bit-map as used */ in get_resource()
46 for (n = multi; n > 0; n--) { in get_resource()
50 i--; in get_resource()
[all …]
|
| /kernel/linux/linux-6.6/sound/pci/ctxfi/ |
| D | ctresource.c | 1 // SPDX-License-Identifier: GPL-2.0-only
21 /* Resource allocation based on bit-map management mechanism */
24 unsigned int multi, unsigned int *ridx) in get_resource() argument
29 for (i = 0, n = multi; i < amount; i++) { in get_resource()
33 n = multi; in get_resource()
36 if (!(--n)) in get_resource()
42 return -ENOENT; in get_resource()
45 /* Mark the contiguous bits in resource bit-map as used */ in get_resource()
46 for (n = multi; n > 0; n--) { in get_resource()
50 i--; in get_resource()
[all …]
|