Searched full:maps (Results 1 – 25 of 205) sorted by relevance
123456789
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | snps,dw-apb-ictl.txt | 20 - 0 maps to bit 0 of low interrupts,
21 - 1 maps to bit 1 of low interrupts,
22 - 32 maps to bit 0 of high interrupts,
23 - 33 maps to bit 1 of high interrupts,
|
| D | marvell,orion-intc.txt | 13 - 0 maps to bit 0 of first base address,
14 - 1 maps to bit 1 of first base address,
15 - 32 maps to bit 0 of second base address, and so on.
|
| /Documentation/bpf/ |
| D | maps.rst | 3 BPF maps
6 BPF 'maps' provide generic storage of different types for sharing data between
10 maps are accessed from BPF programs via BPF helpers which are documented in the
13 BPF maps are accessed from user space via the ``bpf`` syscall, which provides
14 commands to create maps, lookup elements, update elements and delete elements.
56 failure. The map can be deleted by calling ``close(fd)``. Maps held by open
|
| D | map_of_maps.rst | 18 metadata that the outer map holds about its inner maps. This inner map has a
38 the max_entries limit that you specify. Hash maps use pre-allocation of hash
55 Inner maps can be retrieved using the ``bpf_map_lookup_elem()`` helper. This
75 } inner_map1 SEC(".maps"), inner_map2 SEC(".maps");
82 } outer_map SEC(".maps") = {
88 examples of declarative initialisation of outer maps.
|
| D | drgn.rst | 23 `bpf_inspect.py`_ is a tool intended to inspect BPF programs and maps. It can
24 iterate over all programs and maps in the system and print basic information
42 List BPF maps::
80 drgn script to list BPF programs or maps and their properties
91 map (m) list BPF maps
97 information about BPF programs, maps and other objects.
|
| D | map_devmap.rst | 12 ``BPF_MAP_TYPE_DEVMAP`` and ``BPF_MAP_TYPE_DEVMAP_HASH`` are BPF maps primarily
13 used as backend maps for the XDP BPF helper call ``bpf_redirect_map()``.
18 pairs to update the maps with new net devices.
152 } tx_port SEC(".maps");
164 } forward_map SEC(".maps");
|
| D | linux-notes.rst | 23 Maps chapter
26 Linux only supports the 'map_val(map)' operation on array maps with a single element.
28 Linux uses an fd_array to store maps associated with a BPF program. Thus,
|
| D | redirect.rst | 9 Supported maps
19 For more information on these maps, please see the specific map documentation.
|
| D | map_cpumap.rst | 112 } cpu_map SEC(".maps");
119 } cpus_available SEC(".maps");
126 } cpus_iterator SEC(".maps");
|
| D | index.rst | 26 maps
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ti,ina2xx.yaml | 53 the gain value maps directly with the PG bits of the config register.
56 value of 1 maps to ADCRANGE=1 where no gain divisor is applied to the
57 shunt voltage, and a value of 4 maps to ADCRANGE=0 such that a wider
71 of Mask/Enable register. Default value is Normal (0 which maps to
73 (1 which maps to active-high open collector). Specify this property to set
|
| /Documentation/filesystems/ext4/ |
| D | blocks.rst | 63 * - Blocks Per File, Block Maps
73 * - File Size, Block Maps
125 * - Blocks Per File, Block Maps
135 * - File Size, Block Maps
141 Note: Files not using extents (i.e. files using block maps) must be
|
| /Documentation/devicetree/bindings/phy/ |
| D | realtek,usb3phy.yaml | 16 support multiple XHCI controllers. One PHY device node maps to one XHCI
21 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on some
31 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#2.
39 Each xhci maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#0.
|
| D | realtek,usb2phy.yaml | 16 support multiple XHCI controllers. One PHY device node maps to one XHCI
21 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on some
39 Each XHCI maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#2.
47 Each xhci maps to one USB 2.0 PHY and map one USB 3.0 PHY on controllers#0.
55 Each XHCI maps to one USB 2.0 PHY.
|
| /Documentation/bpf/libbpf/ |
| D | libbpf_overview.rst | 22 * Provides BPF-side APIS, including BPF helper definitions, BPF maps support,
36 completely independent), BPF maps, and global variables. The global
46 object file and discovers BPF maps, BPF programs, and global variables. After
52 maps, resolves various relocations, and verifies and loads BPF programs into
62 packets, or updating BPF maps and global variables that can be read from user
66 libbpf detaches BPF programs and unloads them from the kernel. BPF maps are
102 global variables. The skeleton code memory maps global variables as a struct
108 available maps, programs, etc. BPF skeleton provides direct access to all the
109 BPF maps and BPF programs as struct fields. This eliminates the need for
124 maps, manipulate network packets, etc.
|
| /Documentation/power/regulator/ |
| D | machine.rst | 34 This maps Regulator-1 to the 'Vcc' supply for Consumer B and maps Regulator-2
38 for each regulator power domain. This structure also maps the consumers
|
| /Documentation/mm/ |
| D | split_page_table_lock.rst | 17 maps PTE and takes PTE table lock, returns pointer to PTE with
20 maps PTE, returns pointer to PTE with pointer to its PTE table
23 maps PTE, returns pointer to PTE with pointer to its PTE table
27 maps PTE, returns pointer to PTE, or returns NULL if no PTE table;
|
| D | memory-model.rst | 39 maps the entire physical memory. For most architectures, the holes
66 maps for non-volatile memory devices and deferred initialization of
101 initialize the memory sections and the memory maps.
109 and uses high bits of a PFN to access the section that maps that page
|
| /Documentation/admin-guide/device-mapper/ |
| D | persistent-data.rst | 55 The Space Maps
84 The first maps a device id to a mapping tree, and that in turn maps a
|
| /Documentation/ABI/testing/ |
| D | sysfs-block-loop | 15 (RO) The path of the backing file that the loop device maps its
30 (RO) The size (in bytes) that the block device maps, starting
|
| /Documentation/devicetree/bindings/ata/ |
| D | sata_highbank.yaml | 42 description: Maps port numbers to offsets within the SGPIO bitstream.
49 phandle-combophy and lane assignment, which maps each SATA port to a
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | adi,adv7533.yaml | 32 maps. Each map has it own I2C address and acts as a standard slave
40 Names of maps with programmable addresses. It can contain any map
145 * bus. All other maps continue to use their default addresses.
|
| D | adi,adv7511.yaml | 31 maps. Each map has it own I2C address and acts as a standard slave
39 Names of maps with programmable addresses. It can contain any map
189 * bus. All other maps continue to use their default addresses.
|
| /Documentation/devicetree/bindings/display/ |
| D | st,stm32mp25-lvds.yaml | 15 LVDS protocol: it maps the pixels received from the upstream Pixel-DMA (LTDC)
19 - LVDS host: handles the LVDS protocol (FPD / OpenLDI) and maps its input
|
| /Documentation/sound/designs/ |
| D | channel-mapping-api.rst | 10 The channel mapping API allows user to query the possible channel maps
60 maps. A list item of a channel map is usually a TLV of
119 provide multiple channel maps in a TLV container type. The TLV data
|
123456789