Home
last modified time | relevance | path

Searched full:map (Results 1 – 25 of 590) sorted by relevance

12345678910>>...24

/Documentation/bpf/
Dmap_cgroup_storage.rst8 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)
75 Userspace accessing map declared above::
80 __u32 map_lookup(struct bpf_map *map, __u64 cgrp, enum bpf_attach_type type)
87 bpf_map_lookup_elem(bpf_map__fd(map), &key, &value);
115 __u32 map_lookup(struct bpf_map *map, __u64 cgrp, enum bpf_attach_type type)
[all …]
Dmap_of_maps.rst13 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
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.
28 - Any BPF map type can be used as an inner map, except for
30 - A BPF program cannot update or delete outer map entries.
37 map. The kernel is responsible for allocating and freeing key/value pairs, up to
[all …]
Dmap_bloom_filter.rst11 ``BPF_MAP_TYPE_BLOOM_FILTER`` provides a BPF bloom filter map. Bloom
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
31 The ``max_entries`` size that is specified at map creation time is used
38 the lower 4 bits of ``map_extra`` in ``union bpf_attr`` at map creation
43 It is not possible to delete elements from a bloom filter map. A bloom
[all …]
Dmap_cgrp_storage.rst8 The ``BPF_MAP_TYPE_CGRP_STORAGE`` map type represents a local fix-sized
11 data for a particular cgroup can be retrieved by looking up the map
15 ``BPF_MAP_TYPE_CGRP_STORAGE`` map type.
20 The map key must be ``sizeof(int)`` representing a cgroup fd.
23 void *bpf_cgrp_storage_get(struct bpf_map *map, struct cgroup *cgroup, void *value, u64 flags)
30 long bpf_cgrp_storage_delete(struct bpf_map *map, struct cgroup *cgroup)
32 The map is available to all program types.
64 Userspace accessing map declared above::
69 __u32 map_lookup(struct bpf_map *map, int cgrp_fd)
72 value = bpf_map_lookup_elem(bpf_map__fd(map), &cgrp_fd);
[all …]
Dmap_hash.rst16 purpose hash map storage. Both the key and the value can be structs,
35 map type and the flags used to create the map.
40 **BPF_F_NO_COMMON_LRU** Per-CPU LRU, global map Per-CPU LRU, per-cpu map
41 **!BPF_F_NO_COMMON_LRU** Global LRU, global map Global LRU, per-cpu map
55 long bpf_map_update_elem(struct bpf_map *map, const void *key, const void *value, u64 flags)
74 void *bpf_map_lookup_elem(struct bpf_map *map, const void *key)
85 long bpf_map_delete_elem(struct bpf_map *map, const void *key)
103 void *bpf_map_lookup_percpu_elem(struct bpf_map *map, const void *key, u32 cpu)
193 Userspace walking the map elements from the map declared above:
224 aspects of the map implementations that are not considered stable ABI. The
[all …]
Dmap_sk_storage.rst12 programs. A map of type ``BPF_MAP_TYPE_SK_STORAGE`` declares the type of storage
15 locally with each socket instead of with the map. The kernel is responsible for
17 either the map or the socket is deleted.
21 - The ``BPF_F_NO_PREALLOC`` flag must be used when creating a map for
35 void *bpf_sk_storage_get(struct bpf_map *map, void *sk, void *value, u64 flags)
37 Socket-local storage for ``map`` can be retrieved from socket ``sk`` using the
54 long bpf_sk_storage_delete(struct bpf_map *map, void *sk)
56 Socket-local storage for ``map`` can be deleted from socket ``sk`` using the
70 Socket-local storage for map ``map_fd`` can be added or updated locally to a
74 and size of ``value`` should be the same as the value type of the map
[all …]
Dmaps.rst8 hash, array, bloom filter and radix-tree. Several of the map types exist to
9 support specific BPF helpers that perform actions based on the map contents. The
18 Map Types
39 Create a map with the desired type and attributes in ``attr``:
56 failure. The map can be deleted by calling ``close(fd)``. Maps held by open
64 Lookup key in a given map using ``attr->map_fd``, ``attr->key``,
70 Create or update key/value pair in a given map using ``attr->map_fd``, ``attr->key``,
75 Find and delete element by key in a given map using ``attr->map_fd``,
Dmap_sockmap.rst19 index to look up a reference to a ``struct sock``. The map values are socket
20 descriptors. Similarly, ``BPF_MAP_TYPE_SOCKHASH`` is a hash backed BPF map that
26 the map holds to user-space is neither safe nor useful.
36 ``sk_psock`` inherits the programs that are attached to the map.
39 parse or verdict program. If adding a sock object to a map would result
55 programs to the same map.
57 The attach types for the map programs are:
87 long bpf_msg_redirect_map(struct sk_msg_buff *msg, struct bpf_map *map, u32 key, u64 flags)
91 returns ``SK_PASS``), redirect it to the socket referenced by ``map`` (of type
103 long bpf_sk_redirect_map(struct sk_buff *skb, struct bpf_map *map, u32 key u64 flags)
[all …]
Dmap_cpumap.rst12 :doc: cpu map
14 An example use-case for this map type is software based Receive Side Scaling (RSS).
16 The CPUMAP represents the CPUs in the system indexed as the map-key, and the
17 map-value is the config setting (per CPUMAP entry). Each CPUMAP entry has a dedicated
37 long bpf_redirect_map(struct bpf_map *map, u32 key, u64 flags)
39 Redirect the packet to the endpoint referenced by ``map`` at index ``key``.
40 For ``BPF_MAP_TYPE_CPUMAP`` this map contains references to CPUs.
42 The lower two bits of ``flags`` are used as the return code if the map lookup
68 int fd; /* prog fd on map write */
69 __u32 id; /* prog id on map read */
[all …]
/Documentation/networking/device_drivers/cellular/qualcomm/
Drmnet.rst11 Protocol (MAP). This protocol is used by all recent chipsets using Qualcomm
20 packets with MAP headers to rmnet. Based on the multiplexer id, rmnet
21 routes to the appropriate PDN after removing the MAP header.
24 sending aggregated bunch of MAP frames. rmnet driver will de-aggregate
25 these MAP frames and send them to appropriate PDN's.
30 a. MAP packet v1 (data / control)
32 MAP header fields are in big endian format.
42 Command (1)/ Data (0) bit value is to indicate if the packet is a MAP command
53 Payload length includes the padding length but does not include MAP header
56 b. Map packet v4 (data / control)
[all …]
/Documentation/devicetree/bindings/interrupt-controller/
Dfsl,ls-extirq.yaml48 interrupt-map:
51 interrupt-map-mask: true
59 - interrupt-map
60 - interrupt-map-mask
71 interrupt-map:
74 interrupt-map-mask:
87 interrupt-map:
90 interrupt-map-mask:
104 # function to parser interrupt-map. So it doesn't consider '#address-size'
107 # When dt-binding verify interrupt-map, item data matrix is spitted at
[all …]
Drenesas,rza1-irqc.yaml41 interrupt-map:
45 interrupt-map-mask:
56 - interrupt-map
57 - interrupt-map-mask
70 interrupt-map =
79 interrupt-map-mask = <7 0>;
/Documentation/devicetree/bindings/bus/
Dxlnx,versal-net-cdx.yaml22 iommu-map property is used to define the set of stream ids
26 The msi-map property is used to associate the devices with the
41 iommu-map: true
43 msi-map: true
61 - iommu-map
62 - msi-map
76 /* define map for RIDs 250-259 */
77 iommu-map = <250 &smmu 250 10>;
78 /* define msi map for RIDs 250-259 */
79 msi-map = <250 &its 250 10>;
/Documentation/mm/
Dhugetlbfs_reserv.rst38 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
89 - For private mappings, the reservation map hangs off the VMA structure.
90 Specifically, vma->vm_private_data. This reserve map is created at the
92 - For shared mappings, the reservation map hangs off the inode. Specifically,
95 contains a reservation map. As a result, the reservation map is allocated
[all …]
/Documentation/ABI/testing/
Dsysfs-firmware-memmap5 On all platforms, the firmware provides a memory map which the
6 kernel reads. The resources from that memory map are registered
11 map is modified afterwards by the kernel itself, either because
12 the kernel merges that memory map with other information or
13 just because the user overwrites that memory map via command
16 kexec needs the raw firmware-provided memory map to setup the
18 kexec. Also, the raw memory map is useful for debugging. For
20 the raw memory map to userspace.
31 The maximum depends on the number of memory map entries provided
66 map in a human-readable format::
Dsysfs-firmware-efi-runtime-map1 What: /sys/firmware/efi/runtime-map/
14 /sys/firmware/efi/runtime-map/ is the directory the kernel
19 /sys/firmware/efi/runtime-map/0
20 /sys/firmware/efi/runtime-map/1
21 /sys/firmware/efi/runtime-map/2
22 /sys/firmware/efi/runtime-map/3
/Documentation/sound/designs/
Dchannel-mapping-api.rst11 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
29 was no way to specify this because of lack of channel map
46 * name = "Playback Channel Map" or "Capture Channel Map"
54 allow user to change the channel map dynamically.
60 maps. A list item of a channel map is usually a TLV of
68 The ``_FIXED`` type is for a channel map with the fixed channel position
[all …]
/Documentation/devicetree/bindings/pci/
Dxilinx-versal-cpm.yaml38 msi-map:
67 - interrupt-map
68 - interrupt-map-mask
70 - msi-map
89 interrupt-map-mask = <0 0 0 7>;
90 interrupt-map = <0 0 0 1 &pcie_intc_0 0>,
97 msi-map = <0x0 &its_gic 0x0 0x10000>;
116 interrupt-map-mask = <0 0 0 7>;
117 interrupt-map = <0 0 0 1 &pcie_intc_1 0>,
124 msi-map = <0x0 &its_gic 0x0 0x10000>;
Dmediatek,mt7621-pcie.yaml85 - interrupt-map-mask
86 - interrupt-map
100 - interrupt-map-mask
101 - interrupt-map
126 interrupt-map-mask = <0xF800 0 0 0>;
127 interrupt-map = <0x0000 0 0 0 &gic GIC_SHARED 4 IRQ_TYPE_LEVEL_HIGH>,
138 interrupt-map-mask = <0 0 0 0>;
139 interrupt-map = <0 0 0 0 &gic GIC_SHARED 4 IRQ_TYPE_LEVEL_HIGH>;
153 interrupt-map-mask = <0 0 0 0>;
154 interrupt-map = <0 0 0 0 &gic GIC_SHARED 24 IRQ_TYPE_LEVEL_HIGH>;
[all …]
Dmediatek-pcie.txt43 - interrupt-map-mask and interrupt-map: Standard PCI IRQ mapping properties
68 - interrupt-map-mask and interrupt-map: Standard PCI IRQ mapping properties
96 interrupt-map-mask = <0xf800 0 0 0>;
97 interrupt-map = <0x0000 0 0 0 &sysirq GIC_SPI 193 IRQ_TYPE_LEVEL_LOW>,
122 interrupt-map-mask = <0 0 0 0>;
123 interrupt-map = <0 0 0 0 &sysirq GIC_SPI 193 IRQ_TYPE_LEVEL_LOW>;
132 interrupt-map-mask = <0 0 0 0>;
133 interrupt-map = <0 0 0 0 &sysirq GIC_SPI 194 IRQ_TYPE_LEVEL_LOW>;
142 interrupt-map-mask = <0 0 0 0>;
143 interrupt-map = <0 0 0 0 &sysirq GIC_SPI 195 IRQ_TYPE_LEVEL_LOW>;
[all …]
Dversatile.yaml33 interrupt-map:
36 interrupt-map-mask:
48 - interrupt-map
49 - interrupt-map-mask
71 interrupt-map-mask = <0x1800 0 0 7>;
72 interrupt-map = <0x1800 0 0 1 &sic 28>,
Daltr,pcie-root-port.yaml38 interrupt-map-mask:
45 interrupt-map:
60 - interrupt-map
61 - interrupt-map-mask
107 interrupt-map-mask = <0 0 0 7>;
108 interrupt-map = <0 0 0 1 &pcie_0 0 0 0 1>,
/Documentation/filesystems/
Didmappings.rst64 mapping ``k11000`` up to ``u1000``. Afterwards, we can map ``u1000`` down using
66 idmapping would map ``u1000`` down to ``21000``. The third idmapping would map
88 - If we want to map from left to right::
93 - If we want to map from right to left::
203 If we've been given ``k11000`` from one idmapping we can map that id up in
215 /* Map the kernel id up into a userspace id in the second idmapping. */
221 /* Map the userspace id down into a kernel id in the second idmapping. */
224 /* Map the kernel id up into a userspace id in the first idmapping. */
240 ownership information about the file the kernel can't simply map the id back up
244 So the kernel will map the id back up in the idmapping of the caller. Let's
[all …]
/Documentation/driver-api/nvdimm/
Dbtt.rst59 | BTT Map |
76 a. The BTT Map
79 The map is a simple lookup/indirection table that maps an LBA to an internal
80 block. Each map entry is 32 bits. The two most significant bits are special
109 indirection from the map
119 premap ABA is 256G. We now refer to the map, and find out the mapping for block
135 new_map The new postmap ABA. The map will up updated to reflect this
175 the reader consulted a map entry, and started reading the corresponding block. A
177 the map for that external LBA to point to its new postmap ABA. At this point the
190 e. In-memory data structure: map locks
[all …]
/Documentation/devicetree/bindings/power/reset/
Dsyscon-poweroff.yaml13 This is a generic poweroff driver using syscon to map the poweroff register.
15 defined by the register map pointed by syscon reference plus the offset
18 The SYSCON register map is normally retrieved from the parental dt-node. So
32 description: Offset in the register map for the poweroff register (in bytes).
38 Phandle to the register map node. This property is deprecated in favor of

12345678910>>...24