Searched full:lookup (Results 1 – 25 of 158) sorted by relevance
1234567
| /Documentation/bpf/ |
| D | prog_sk_lookup.rst | 8 into the socket lookup performed by the transport layer when a packet is to be
31 latency spikes during socket lookup.
54 ``SK_PASS`` signifies that the socket lookup should continue on to regular
55 hashtable-based lookup, while ``SK_DROP`` causes the transport layer to drop the
69 is used as the result of the socket lookup.
73 selected a socket, socket lookup fails.
75 socket lookup continues on.
81 receives information about the packet that triggered the socket lookup. Namely:
|
| D | map_devmap.rst | 15 the index to lookup a reference to a net device. While ``BPF_MAP_TYPE_DEVMAP_HASH``
16 is backed by a hash table that uses a key to lookup a reference to a net device.
26 devmap; only the lookup and insertion is different.
42 The lower two bits of *flags* are used as the return code if the map lookup
58 lower bits of the ``flags`` argument if the map lookup fails.
|
| D | maps.rst | 14 commands to create maps, lookup elements, update elements and delete elements.
64 Lookup key in a given map using ``attr->map_fd``, ``attr->key``,
|
| D | map_lpm_trie.rst | 19 of 8, in the range from 8 to 2048. The key used for lookup and update
139 The following BPF code snippet shows how to lookup by IPv4 address:
143 void *lookup(__u32 ipaddr)
|
| D | map_bloom_filter.rst | 41 positive rate and the speed of a lookup.
128 void *lookup(__u32 key)
132 * value using a secondary lookup, e.g. in a hash table
|
| /Documentation/filesystems/ |
| D | path-lookup.txt | 1 Path walking and name lookup locking
9 path string. Then repeating the lookup from the child dentry and finding its
16 Prior to 2.5.10, dcache_lock was acquired in d_lookup (dcache hash lookup) and
50 current->fs->cwd or current->fs->root) as the first parent of the lookup. Then
53 parent for the next lookup.
58 Turning the child into a parent for the next lookup requires more checks and
72 - lookup and create missing parts of the path on demand.
77 Dcache name lookup
79 In order to lookup a dcache (parent, name) tuple, we take a hash on the tuple
115 lookup of the old list veering off into the new (incorrect) list and missing
[all …]
|
| D | path-lookup.rst | 2 Pathname lookup
7 - <https://lwn.net/Articles/649115/> Pathname lookup in Linux
8 - <https://lwn.net/Articles/649729/> RCU-walk: faster pathname lookup in Linux
15 - per-directory parallel name lookup.
18 Introduction to pathname lookup
21 The most obvious aspect of pathname lookup, which very little
96 changes that affect that lookup. One fairly extreme case is that if
100 pathname lookup is to prevent them from having damaging effects. Many
103 pathname lookup.
109 make them quickly available for lookup. Each entry (known as a
[all …]
|
| D | squashfs.rst | 154 | lookup table |
162 written the completed inode, directory, fragment, export, uid/gid lookup and
214 file lookup. Directory indexes store one entry per metablock, each entry
217 and at lookup the index is scanned linearly looking for the first filename
221 decompressed to do a lookup irrespective of the length of the directory.
244 3.5 Fragment lookup table
248 location on disk and compressed size using a fragment lookup table. This
249 fragment lookup table is itself stored compressed into metadata blocks.
254 3.6 Uid/gid lookup table
268 an inode number to inode disk location lookup table. This is required to
[all …]
|
| D | directory-locking.rst | 73 in its own right; it may happen as part of lookup. We speak of the
84 to another and we run into it when we do a lookup.
87 only once. Multiple aliases are not allowed. So when lookup runs into
89 dcache trees. Lookup is already holding the parent locked. If alias is
91 lookup in, under the name we'd been looking for. If the alias is already
96 and fail the lookup if it is. Then we try to lock the filesystem and the
97 current parent of the alias. If either trylock fails, we fail the lookup.
243 an unrelated lookup splice a distant ancestor of source to some distant
|
| D | files.rst | 66 take care of barrier requirements due to lock-free lookup.
108 On newer kernels rcu based file lookup has been switched to rely on
119 without first acquiring a reference on it under rcu lookup. Not doing
|
| /Documentation/driver-api/firmware/ |
| D | direct-fs-lookup.rst | 2 Direct filesystem lookup
5 Direct filesystem lookup is the most common form of firmware lookup performed
8 The filesystem lookup is implemented in fw_get_filesystem_firmware(), it
|
| D | core.rst | 13 direct-fs-lookup
15 lookup-order
|
| D | lookup-order.rst | 2 Firmware lookup order
13 * The ''Direct filesystem lookup'' is performed next, if found we
|
| /Documentation/devicetree/bindings/thermal/ |
| D | generic-adc-thermal.yaml | 16 temperature using voltage-temperature lookup table.
33 temperature-lookup-table:
35 Lookup table to map the relation between ADC value and temperature.
63 temperature-lookup-table = <
|
| /Documentation/arch/powerpc/ |
| D | associativity.rst | 59 "ibm,numa-lookup-index-table" property contains a list of one or more numbers representing
67 "ibm,numa-lookup-index-table" = {4, 0, 8, 250, 252}. The offset of domainID 8 (2) is used when
77 numa-lookup-index-table.
80 ibm,numa-lookup-index-table = <3 0 8 40>;
102 "ibm,lookup-index-table" helps in having a compact representation of distance matrix.
104 With "ibm,lookup-index-table" we can achieve a compact representation of
|
| /Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,bcm63138.txt | 11 An optional Boot lookup table Device Tree node is required for secondary CPU
16 Required properties for the Boot lookup table node:
18 - reg: register base address and length for the Boot Lookup table
|
| /Documentation/filesystems/nfs/ |
| D | exporting.rst | 48 2. The dcache must be prepared for a newly found (via ->lookup) directory
51 ->lookup). This is particularly needed for directories as
81 loose directory dentries at lookup time. They are:
96 convention of ->lookup.
105 when ->lookup finds an inode for a given parent and name.
113 Typically the ->lookup routine will simply end with a::
142 so any filehandle lookup that requires finding a parent will fail.
143 ->lookup("..") is *not* used as a default as it can leave ".." entries
|
| /Documentation/admin-guide/gpio/ |
| D | gpio-virtuser.rst | 46 Creating GPIO lookup tables
53 The ``'con_id'`` directory represents a single GPIO lookup and its value maps
57 Users can assign a number of GPIOs to each lookup. Each GPIO is a sub-directory
74 For virtual consumers created using configfs we use machine lookup tables so
81 chip to lookup while ``'offset'`` represents the offset of the line in that
84 The remaining attributes map to the ``'flags'`` field of the GPIO lookup
|
| /Documentation/RCU/ |
| D | rculist_nulls.rst | 32 1) Lookup algorithm
149 the lookup met the end of chain. If final 'nulls' value
150 is not the slot number, then we must restart the lookup at
159 1) lookup algorithm
182 // If the nulls value we got at the end of this lookup is
183 // not the expected one, we must restart lookup.
|
| /Documentation/leds/ |
| D | leds-qcom-lpg.rst | 11 number of PWM channels, a programmable pattern lookup table and a RGB LED
24 lookup table of brightness values and per channel properties to select the
72 In order to save space in the shared lookup table the LPG supports "ping-pong"
|
| /Documentation/networking/ |
| D | fib_trie.rst | 68 straightforward trie lookup.
119 Main lookup mechanism
121 fn_trie_lookup() is the main lookup function.
123 The lookup is in its simplest form just like fib_find_node(). We descend the
|
| D | xfrm_proc.rst | 77 …State direction mismatch (lookup found an output state on the input path, expected input or no dir…
119 …State direction mismatch (lookup found an input state on the output path, expected output or no di…
|
| D | mctp.rst | 272 : route lookup
288 : route lookup
290 : sk_key lookup
296 : route lookup
298 : sk_key lookup
302 : route lookup
304 : sk_key lookup
|
| D | dns_resolver.rst | 87 set lookup.
101 DNS lookup failed.
122 this type are used to transport and cache DNS lookup results from userspace.
|
| /Documentation/devicetree/bindings/display/ |
| D | solomon,ssd1307fb.yaml | 102 solomon,lookup-table:
240 solomon,lookup-table = /bits/ 8 <0x3f 0x3f 0x3f 0x3f>;
267 solomon,lookup-table = /bits/ 8 <0x3f 0x3f 0x3f 0x3f>;
|
1234567