Searched full:hash (Results 1 – 25 of 156) sorted by relevance
1234567
| /Documentation/devicetree/bindings/crypto/ |
| D | img-hash.txt | 1 Imagination Technologies hardware hash accelerator
3 The hash accelerator provides hardware hashing acceleration for
8 - compatible : "img,hash-accelerator"
14 - clock-names : "sys" Used to clock the hash block registers
15 "hash" Used to clock data through the accelerator
19 hash: hash@18149600 {
20 compatible = "img,hash-accelerator";
26 clock-names = "sys", "hash";
|
| D | st,stm32-hash.yaml | 4 $id: http://devicetree.org/schemas/crypto/st,stm32-hash.yaml#
7 title: STMicroelectronics STM32 HASH
9 description: The STM32 HASH block is built on the HASH block found in
19 - st,stn8820-hash
20 - stericsson,ux500-hash
21 - st,stm32f456-hash
22 - st,stm32f756-hash
23 - st,stm32mp13-hash
68 const: stericsson,ux500-hash
83 hash@54002000 {
[all …]
|
| D | nvidia,tegra234-se-hash.yaml | 4 $id: http://devicetree.org/schemas/crypto/nvidia,tegra234-se-hash.yaml#
7 title: NVIDIA Tegra Security Engine for HASH algorithms
10 The Tegra Security HASH Engine accelerates the following HASH functions -
19 const: nvidia,tegra234-se-hash
46 compatible = "nvidia,tegra234-se-hash";
|
| D | aspeed,ast2500-hace.yaml | 7 title: ASPEED HACE hash and crypto Hardware Accelerator Engines
13 The Hash and Crypto Engine (HACE) is designed to accelerate the throughput
14 of hash data digest, encryption, and decryption. Basically, HACE can be
15 divided into two independently engines - Hash Engine and Crypto Engine.
|
| /Documentation/admin-guide/device-mapper/ |
| D | verity.rst | 21 This is the type of the on-disk hash format.
37 This is the device that supplies the hash tree data. It may be
44 Each block corresponds to one digest on the hash device.
47 The size of a hash block in bytes.
56 to the root block of the hash tree.
59 The cryptographic hash algorithm used for this device. This should
63 The hexadecimal encoding of the cryptographic hash of the root hash block
64 and the salt. This hash should be trusted as there is no other authenticity
96 Use forward error correction (FEC) to recover from corruption if hash
98 may be the same device where data and hash blocks reside, in which case
[all …]
|
| D | vdo-design.rst | 91 Inaccuracy can also result from a hash collision where two different blocks
93 vdo does not use a cryptographic hash, a malicious workload could be
156 allows the index to use many fewer bytes per entry than a traditional hash
430 The data_vio's data is hashed and the hash (the "record name") is
434 the data_vios currently writing the same data. Active hash locks are
437 the hash zone.
439 If there is no existing hash lock for this data_vio's record_name, the
440 data_vio obtains a hash lock from the pool, adds it to the hashtable,
441 and sets itself as the new hash lock's "agent." The hash_lock pool is
442 also covered by the implicit hash zone lock. The hash lock agent will
[all …]
|
| /Documentation/crypto/ |
| D | api-digest.rst | 4 .. kernel-doc:: include/crypto/hash.h
7 .. kernel-doc:: include/crypto/hash.h
13 .. kernel-doc:: include/crypto/hash.h
16 .. kernel-doc:: include/crypto/hash.h
19 Asynchronous Hash Request Handle
22 .. kernel-doc:: include/crypto/hash.h
23 :doc: Asynchronous Hash Request Handle
25 .. kernel-doc:: include/crypto/hash.h
31 .. kernel-doc:: include/crypto/hash.h
34 .. kernel-doc:: include/crypto/hash.h
|
| D | devel-algos.rst | 9 while the other two are specific to HASH transformations and
136 Hashing [HASH]
144 There are multiple ways to register a HASH transformation, depending on
146 [AHASH] and the amount of HASH transformations we are registering. You
147 can find the prototypes defined in include/crypto/internal/hash.h:
157 The respective counterparts for unregistering the HASH transformation
184 '----' '---> HASH
190 '----' '---> HASH
196 '---------------> HASH
233 Specifics Of Asynchronous HASH Transformation
|
| /Documentation/pcmcia/ |
| D | devicetable.rst | 23 If the hash is incorrect, the kernel will inform you about this in "dmesg"
24 upon module initialization, and tell you of the correct hash.
26 You can determine the hash of the product ID strings by catting the file
31 The hex value after "pa" is the hash of product ID string 1, after "pb" for
35 to determine the crc32 hash. Simply pass the string you want to evaluate
|
| /Documentation/bpf/ |
| D | map_hash.rst | 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
21 of hash table elements by default. The ``BPF_F_NO_PREALLOC`` flag can be
28 variants add LRU semantics to their respective hash tables. An LRU hash
29 will automatically evict the least recently used entries when the hash
30 table reaches capacity. An LRU hash maintains an internal LRU list that
57 Hash entries can be added or updated using the ``bpf_map_update_elem()``
76 Hash entries can be retrieved using the ``bpf_map_lookup_elem()``
87 Hash entries can be deleted using the ``bpf_map_delete_elem()``
96 automatically access the hash slot for the current CPU.
[all …]
|
| /Documentation/ABI/testing/ |
| D | devlink-resource-mlxsw | 8 is divided into two sections, the first is hash-based table
10 between the linear and hash-based sections is static and
24 Description: The hash based section of the KVD is managed by the switch
32 Description: The hash based section of the KVD is managed by the switch
|
| D | sysfs-driver-intel-m10-bmc-sec-update | 5 Description: Read only. Returns the root entry hash for the static
7 string: "hash not programmed". This file is only
15 Description: Read only. Returns the root entry hash for the partial
17 returns the string: "hash not programmed". This file
25 Description: Read only. Returns the root entry hash for the BMC image
27 "hash not programmed". This file is only visible if the
|
| D | sysfs-bus-pci-devices-catpt | 15 build hash and log-providers hash. This information is
|
| /Documentation/filesystems/ext4/ |
| D | directory.rst | 125 must also include hash information in the directory entry. We append
141 - hash
142 - The hash of the directory name
146 - The minor hash of the directory name
191 Hash Tree Directories
196 balanced tree keyed off a hash of the directory entry name. If the
210 the root node contains metadata about the tree and finally a hash->block
214 node, which is indexed by a minor hash. Interior nodes in this tree
218 (presumably) hash to the same value. If there is an overflow, the
220 least-significant bit of the hash (in the interior node map) that gets
[all …]
|
| /Documentation/filesystems/ |
| D | fsverity.rst | 29 Userspace can use another ioctl to retrieve the root hash (actually
30 the "fs-verity file digest", which is a hash that includes the Merkle
31 tree root hash) that fs-verity is enforcing for the file. This ioctl
34 fs-verity is essentially a way to hash a file in constant time,
35 subject to the caveat that reads which would violate the hash will
44 However, because fs-verity makes retrieving the file hash extremely
49 A standard file hash could be used instead of fs-verity. However,
55 read and hash the entire file before starting the application.
57 Unlike an ahead-of-time hash, fs-verity also re-verifies data each
128 - ``hash_algorithm`` must be the identifier for the hash algorithm to
[all …]
|
| D | ubifs-authentication.rst | 260 with a hash over each node's child nodes. As a result, the index basically also
265 can be hooked to recompute the hash only for each changed node at the same time.
270 keyed hash (HMAC) over its own contents and a hash of the root node of the index
275 include a hash. All other types of nodes will remain unchanged. This reduces
283 | (hash) |
291 | (hash) (hash) |
302 | (hash) (hash) | | (hash) (hash) |
311 Figure 3: Coverage areas of index node hash and master node HMAC
316 persist the hash and file contents. Here the existing UBIFS logic for how
319 hashes to index nodes does not change this since each hash will be persisted
[all …]
|
| /Documentation/networking/ |
| D | scaling.rst | 38 The filter used in RSS is typically a hash function over the network
39 and/or transport layer headers-- for example, a 4-tuple hash over
43 by masking out the low order seven bits of the computed hash for the
44 packet (usually a Toeplitz hash), taking this number as a key into the
49 are swapped, the computed hash is the same. This is beneficial in some
52 "Symmetric-XOR" is a type of RSS algorithms that achieves this hash
80 hash, is usually programmed by the driver at initialization. The
143 RX flow hash indirection table for eth0 with 13 RX ring(s):
149 RX flow hash indirection table for eth0 with 13 RX ring(s):
178 2) software filters can easily be added to hash over new protocols
[all …]
|
| D | nexthop-group-resilient.rst | 12 the legacy multipath next-hop group, which uses the hash-threshold
15 To select a next hop, hash-threshold algorithm first assigns a range of
17 comparing the SKB hash with the individual ranges. When a next hop is
19 reassignment of parts of hash space from one next hop to another. RFC 2992
29 under the hash-threshold algorithm.
31 Note how next hop 2 gave up part of the hash space in favor of next hop 1,
37 this hash space reassignment causes an issue that packets from a single
47 insert another layer of indirection between the hash space and its
48 constituent next hops: a hash table. The selection algorithm uses SKB hash
49 to choose a hash table bucket, then reads the next hop that this bucket
[all …]
|
| /Documentation/security/ |
| D | IMA-templates.rst | 9 The original ``ima`` template is fixed length, containing the filedata hash
10 and pathname. The filedata hash is limited to 20 bytes (md5/sha1).
66 calculated with the SHA1 or MD5 hash algorithm;
68 - 'd-ng': the digest of the event, calculated with an arbitrary hash
69 algorithm (field format: <hash algo>:digest);
71 (field format: <digest type>:<hash algo>:digest);
75 or the EVM portable signature, if 'security.ima' contains a file hash.
77 - 'buf': the buffer data that was used to generate the hash without size limitations;
|
| /Documentation/networking/device_drivers/ethernet/microsoft/ |
| D | netvsc.rst | 29 For TCP & UDP, we can switch hash level between L3 and L4 by ethtool
31 hash level is L4. We currently only allow switching TX hash level
41 ethtool -N eth0 rx-flow-hash udp4 sdfn
45 ethtool -N eth0 rx-flow-hash udp4 sd
47 To show UDP hash level::
49 ethtool -n eth0 rx-flow-hash udp4
|
| /Documentation/power/ |
| D | s2ram.rst | 46 hash matches drivers/base/power/resume.c:28
47 hash matches device 0000:01:00.0
54 If no device matches the hash (or any matches appear to be false positives),
56 until after the hash is checked. You can check the hash against the current
|
| /Documentation/networking/device_drivers/ethernet/freescale/ |
| D | gianfar.rst | 33 The gianfar driver supports using the group hash table on the
34 TSEC (and the extended hash table on the eTSEC) for multicast
36 before the hash tables. See Linux documentation on how to join
|
| D | dpaa.rst | 157 ethtool. Also, rx-flow-hash and rx-hashing was added. The addition of RSS
191 hardware frame queues using a hash on IP v4/v6 source and destination
207 FQ (hash result) to another CPU. The ingress traffic arriving on one
214 # ethtool -N fm1-mac9 rx-flow-hash tcp4 ""
216 To turn it back on, one needs to set rx-flow-hash for tcp4/6 or udp4/6::
218 # ethtool -N fm1-mac9 rx-flow-hash udp4 sfdn
224 Besides using the FMan Keygen computed hash for spreading traffic on the
225 128 Rx FQs, the DPAA Ethernet driver also sets the skb hash value when
230 # ethtool -k fm1-mac9 | grep hash
235 # ethtool -k fm1-mac9 | grep hash
|
| /Documentation/netlink/specs/ |
| D | ovs_flow.yaml | 280 name: ovs-action-hash
284 name: hash-alg
286 doc: Algorithm used to compute hash prior to recirculation.
288 name: hash-basis
290 doc: Basis used for computing hash.
292 name: ovs-hash-alg
293 enum-name: ovs-hash-alg
296 Data path hash algorithm for computing Datapath hash. The algorithm type only specifies
297 the fields in a flow will be used as part of the hash. Each datapath is free to use its
298 own hash algorithm. The hash value will be opaque to the user space daemon.
[all …]
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | fm10k.rst | 105 rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6
106 Retrieves the hash options for the specified network traffic type.
111 rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|tcp6|udp6|ah6|esp6|sctp6 m|v|t|s|d|f|n|r
112 Configures the hash options for the specified network traffic type.
116 - f Hash on bytes 0 and 1 of the Layer 4 header of the rx packet.
117 - n Hash on bytes 2 and 3 of the Layer 4 header of the rx packet.
|
1234567