Searched +full:no +full:- +full:map (Results 1 – 25 of 306) sorted by relevance
12345678910>>...13
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smem.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andy Gross <agross@kernel.org>
11 - Bjorn Andersson <bjorn.andersson@linaro.org>
15 reserved-memory used to share data between various subsystems and OSes in
25 memory-region:
32 qcom,rpm-msg-ram:
36 no-map: true
39 - compatible
[all …]
|
| /Documentation/core-api/irq/ |
| D | irq-domain.rst | 9 that each one gets assigned non-overlapping allocations of Linux
24 For this reason we need a mechanism to separate controller-local
29 the controller-local IRQ (hwirq) number into the Linux IRQ number
55 the hwirq, and call the .map() callback so the driver can perform any
61 - irq_resolve_mapping() returns a pointer to the irq_desc structure
62 for a given domain and hwirq number, and NULL if there was no
64 - irq_find_mapping() returns a Linux IRQ number for a given domain and
65 hwirq number, and 0 if there was no mapping
66 - irq_linear_revmap() is now identical to irq_find_mapping(), and is
68 - generic_handle_domain_irq() handles an interrupt described by a
[all …]
|
| /Documentation/mm/ |
| D | hugetlbfs_reserv.rst | 8 Huge pages as described at Documentation/admin-guide/mm/hugetlbpage.rst are
11 are to be used. If no huge page exists at page fault time, the task is sent
34 This is a global (per-hstate) count of reserved huge pages. Reserved
37 as (``free_huge_pages - resv_huge_pages``).
38 Reserve Map
39 A reserve map is described by the structure::
50 There is one reserve map for each huge page mapping in the system.
65 These are stored in the bottom bits of the reservation map pointer.
80 Reservation Map Location (Private or Shared)
86 semantics of the reservation map is significantly different for the two types
[all …]
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | rmem.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
13 - $ref: nvmem.yaml#
18 - enum:
19 - raspberrypi,bootloader-config
20 - raspberrypi,bootloader-public-key
21 - const: nvmem-rmem
26 no-map:
[all …]
|
| /Documentation/sound/designs/ |
| D | channel-mapping-api.rst | 2 ALSA PCM channel-mapping API
11 and the current channel map, also optionally to modify the channel map
14 A channel map is an array of position for each PCM channel.
15 Typically, a stereo PCM stream has a channel map of
17 while a 4.0 surround PCM stream has a channel map of
20 The problem, so far, was that we had no standard channel map
21 explicitly, and applications had no way to know which channel
29 was no way to specify this because of lack of channel map
38 the kernel/user-space ABI perspective. It uses only the existing
46 * name = "Playback Channel Map" or "Capture Channel Map"
[all …]
|
| /Documentation/bpf/ |
| D | map_bloom_filter.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
9 - ``BPF_MAP_TYPE_BLOOM_FILTER`` was introduced in kernel version 5.16
11 ``BPF_MAP_TYPE_BLOOM_FILTER`` provides a BPF bloom filter map. Bloom
12 filters are a space-efficient probabilistic data structure used to
16 The bloom filter map does not have keys, only values. When the bloom
17 filter map is created, it must be created with a ``key_size`` of 0. The
18 bloom filter map supports two operations:
20 - push: adding an element to the map
21 - peek: determining whether an element is present in the map
24 bloom filter map and ``bpf_map_peek_elem`` to query the map. These
[all …]
|
| D | map_of_maps.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
9 - ``BPF_MAP_TYPE_ARRAY_OF_MAPS`` and ``BPF_MAP_TYPE_HASH_OF_MAPS`` were
13 purpose support for map in map storage. One level of nesting is supported, where
14 an outer map contains instances of a single type of inner map, for example
15 ``array_of_maps->sock_map``.
17 When creating an outer map, an inner map instance is used to initialize the
18 metadata that the outer map holds about its inner maps. This inner map has a
19 separate lifetime from the outer map and can be deleted after the outer map has
22 The outer map supports element lookup, update and delete from user space using
24 map.
[all …]
|
| D | map_hash.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
3 .. Copyright (C) 2022-2023 Isovalent, Inc.
10 - ``BPF_MAP_TYPE_HASH`` was introduced in kernel version 3.19
11 - ``BPF_MAP_TYPE_PERCPU_HASH`` was introduced in version 4.6
12 - Both ``BPF_MAP_TYPE_LRU_HASH`` and ``BPF_MAP_TYPE_LRU_PERCPU_HASH``
16 purpose hash map storage. Both the key and the value can be structs,
20 to the max_entries limit that you specify. Hash maps use pre-allocation
22 used to disable pre-allocation when it is too memory expensive.
25 CPU. The per-cpu values are stored internally in an array.
35 map type and the flags used to create the map.
[all …]
|
| D | map_cgroup_storage.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
8 The ``BPF_MAP_TYPE_CGROUP_STORAGE`` map type represents a local fix-sized
13 The map provide a local storage at the cgroup that the BPF program is attached
19 ``BPF_MAP_TYPE_CGROUP_STORAGE`` map type. Some of its behaviors was changed in
25 The map uses key of type of either ``__u64 cgroup_inode_id`` or
38 map will share the same storage. Otherwise, if the type is
44 void *bpf_get_local_storage(void *map, u64 flags)
48 There is no implicit synchronization. Storages of ``BPF_MAP_TYPE_CGROUP_STORAGE``
75 Userspace accessing map declared above::
80 __u32 map_lookup(struct bpf_map *map, __u64 cgrp, enum bpf_attach_type type)
[all …]
|
| D | graph_ds_impl.rst | 5 This document describes implementation details of new-style "graph" data
9 Although no specific verifier code is referred to in this document, the document
14 these graph data structures. **No guarantees** of stability for either
22 ------------
24 The BPF map API has historically been the main way to expose data structures
26 with the map API (HASH, ARRAY), others less so. Consequently, programs
30 Luckily, some restrictions which necessitated the use of BPF map semantics are
31 no longer relevant. With the introduction of kfuncs, kptrs, and the any-context
35 Two such data structures - linked_list and rbtree - have many verification
44 ------------
[all …]
|
| D | ringbuf.rst | 12 ----------
18 - more efficient memory utilization by sharing ring buffer across CPUs;
19 - preserving ordering of events that happen sequentially in time, even across
23 Both are a result of a choice to have per-CPU perf ring buffer. Both can be
25 problem could technically be solved for perf buffer with some in-kernel
30 ------------------
32 Single ring buffer is presented to BPF programs as an instance of BPF map of
46 Another approach could introduce a new concept, alongside BPF map, to represent
51 themselves with, new syntax in libbpf, etc. But then would really provide no
52 additional benefits over the approach of using a map. ``BPF_MAP_TYPE_RINGBUF``
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | mstar,mst-intc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/mstar,mst-intc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Mark-PK Tsai <mark-pk.tsai@mediatek.com>
21 const: mstar,mst-intc
23 interrupt-controller: true
25 "#interrupt-cells":
33 mstar,irqs-map-range:
37 $ref: /schemas/types.yaml#/definitions/uint32-matrix
[all …]
|
| D | open-pic.txt | 13 - compatible: Specifies the compatibility list for the PIC. The type
14 shall be <string> and the value shall include "open-pic".
16 - reg: Specifies the base physical address(s) and size(s) of this
17 PIC's addressable register space. The type shall be <prop-encoded-array>.
19 - interrupt-controller: The presence of this property identifies the node
20 as an Open PIC. No property value shall be defined.
22 - #interrupt-cells: Specifies the number of cells needed to encode an
25 - #address-cells: Specifies the number of cells needed to encode an
27 'interrupt-map' nodes do not have to specify a parent unit address.
31 - pic-no-reset: The presence of this property indicates that the PIC
[all …]
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | google,open-dice.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/google,open-dice.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
13 See https://pigweed.googlesource.com/open-dice/
16 - David Brazdil <dbrazdil@google.com>
19 - $ref: reserved-memory.yaml
23 const: google,open-dice
26 description: page-aligned region of memory containing DICE data
29 - compatible
[all …]
|
| D | nvidia,tegra264-bpmp-shmem.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/nvidia,tegra264-bpmp-shmem.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Tegra CPU-NS - BPMP IPC reserved memory
10 - Peter De Schrijver <pdeschrijver@nvidia.com>
13 Define a memory region used for communication between CPU-NS and BPMP.
15 has to be known to both CPU-NS and BPMP for correct IPC operation.
16 The memory region is defined using a child node under /reserved-memory.
17 The sub-node is named shmem@<address>.
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-mmap.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _dmx-mmap:
13 dmx-mmap - Map device memory into application address space
20 .. code-block:: c
31 Map the buffer to this address in the application's address space.
38 Length of the memory area to map. This must be a multiple of the
54 ``MAP_FIXED`` requests that the driver selects no other address than
62 other (e. g. child-) processes.
80 The :c:func:`mmap()` function asks to map ``length`` bytes starting at
95 error ``MAP_FAILED`` (-1) is returned, and the ``errno`` variable is set
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | vdo-design.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
4 Design of dm-vdo
7 The dm-vdo (virtual data optimizer) target provides inline deduplication,
8 compression, zero-block elimination, and thin provisioning. A dm-vdo target
12 production environments ever since. It was made open-source in 2017 after
14 dm-vdo. For usage, see vdo.rst in the same directory as this file.
20 of 14:1. All zero blocks consume no storage at all.
25 The design of dm-vdo is based on the idea that deduplication is a two-part
27 storing multiple copies of those duplicates. Therefore, dm-vdo has two main
29 duplicate data, and a data store with a reference counted block map that
[all …]
|
| D | vdo.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
3 dm-vdo
6 The dm-vdo (virtual data optimizer) device mapper target provides
7 block-level deduplication, compression, and thin provisioning. As a device
20 https://github.com/dm-vdo/vdo/
25 enter or come up in read-only mode. Because read-only mode is indicative of
26 data-loss, a positive action must be taken to bring vdo out of read-only
28 prepare a read-only vdo to exit read-only mode. After running this tool,
34 inspect a vdo target's on-disk metadata. Fortunately, these tools are
35 rarely needed except by dm-vdo developers.
[all …]
|
| /Documentation/devicetree/bindings/dsp/ |
| D | fsl,dsp.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Daniel Baluta <daniel.baluta@nxp.com>
11 - Shengjiu Wang <shengjiu.wang@nxp.com>
15 advanced pre- and post- audio processing.
20 - fsl,imx8qxp-dsp
21 - fsl,imx8qm-dsp
22 - fsl,imx8mp-dsp
23 - fsl,imx8ulp-dsp
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | func-mmap.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _func-mmap:
13 v4l2-mmap - Map device memory into application address space
18 .. code-block:: c
29 Map the buffer to this address in the application's address space.
36 Length of the memory area to map. This must be the same value as
39 single-planar API, and the same value as returned by the driver in
41 the multi-planar API.
69 ``MAP_FIXED`` requests that the driver selects no other address than
77 other (e. g. child-) processes.
[all …]
|
| /Documentation/devicetree/bindings/pci/ |
| D | rockchip,rk3399-pcie.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/rockchip,rk3399-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Shawn Lin <shawn.lin@rock-chips.com>
13 - $ref: /schemas/pci/pci-host-bridge.yaml#
14 - $ref: rockchip,rk3399-pcie-common.yaml#
18 const: rockchip,rk3399-pcie
22 reg-names:
24 - const: axi-base
[all …]
|
| D | pci-iommu.txt | 22 and a mechanism is required to map from a PCI device to its IOMMU and sideband
33 -------------------
35 - iommu-map: Maps a Requester ID to an IOMMU and associated IOMMU specifier
39 (rid-base,iommu,iommu-base,length).
41 Any RID r in the interval [rid-base, rid-base + length) is associated with
42 the listed IOMMU, with the IOMMU specifier (r - rid-base + iommu-base).
44 - iommu-map-mask: A mask to be applied to each Requester ID prior to being
45 mapped to an IOMMU specifier per the iommu-map property.
52 #address-cells = <1>;
53 #size-cells = <1>;
[all …]
|
| D | brcm,stb-pcie.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/brcm,stb-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jim Quinlan <james.quinlan@broadcom.com>
15 - enum:
16 - brcm,bcm2711-pcie # The Raspberry Pi 4
17 - brcm,bcm4908-pcie
18 - brcm,bcm7211-pcie # Broadcom STB version of RPi4
19 - brcm,bcm7216-pcie # Broadcom 7216 Arm
[all …]
|
| /Documentation/networking/ |
| D | scaling.rst | 1 .. SPDX-License-Identifier: GPL-2.0
13 multi-processor systems.
17 - RSS: Receive Side Scaling
18 - RPS: Receive Packet Steering
19 - RFS: Receive Flow Steering
20 - Accelerated Receive Flow Steering
21 - XPS: Transmit Packet Steering
28 (multi-queue). On reception, a NIC can send different packets to different
33 generally known as “Receive-side Scaling” (RSS). The goal of RSS and
35 Multi-queue distribution can also be used for traffic prioritization, but
[all …]
|
| /Documentation/devicetree/bindings/misc/ |
| D | fsl,qoriq-mc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/misc/fsl,qoriq-mc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Frank Li <Frank.Li@nxp.com>
13 The Freescale Management Complex (fsl-mc) is a hardware resource
15 network-oriented packet processing applications. After the fsl-mc
22 For an overview of the DPAA2 architecture and fsl-mc bus see:
26 same hardware "isolation context" and a 10-bit value called an ICID
31 between ICIDs and IOMMUs, so an iommu-map property is used to define
[all …]
|
12345678910>>...13