| /Documentation/crypto/ |
| D | api-intro.rst | 35 [algorithm api] (for registering algorithms)
37 The idea is to make the user interface and algorithm registration API
103 When submitting a new algorithm for inclusion, a mandatory requirement
204 SHA1 algorithm contributors:
207 DES algorithm contributors:
212 Blowfish algorithm contributors:
216 Twofish algorithm contributors:
220 SHA256/384/512 algorithm contributors:
225 AES algorithm contributors:
233 CAST5 algorithm contributors:
[all …]
|
| D | api-skcipher.rst | 1 Block Cipher Algorithm Definitions
5 :doc: Block Cipher Algorithm Definitions
|
| D | api-digest.rst | 1 Message Digest Algorithm Definitions
5 :doc: Message Digest Algorithm Definitions
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-adc-mcp3564 | 22 auto-zeroing algorithm (the input multiplexer and the ADC
23 include an offset cancellation algorithm that cancels the offset
24 contribution of the ADC). When the offset cancellation algorithm
28 case where the algorithm is disabled. This technique allows the
41 This attribute is used to enable the chopping algorithm for the
48 limitation, the buffer includes an auto-zeroing algorithm that
|
| D | sysfs-kernel-mm-swap | 11 If set to true, the VMA based swap readahead algorithm
13 VMA, and the global swap readahead algorithm will be
15 false, the global swap readahead algorithm will be
|
| /Documentation/networking/ |
| D | net_dim.rst | 21 processing. The mechanism includes an algorithm which decides if and how to
24 iteration of the algorithm, it analyses a given sample of the data, compares it
30 the algorithm might decide not to change anything. The configuration fields are
32 number of wanted packets per event. The Net DIM algorithm ascribes importance to
36 Net DIM Algorithm
39 Each iteration of the Net DIM algorithm follows these steps:
54 compared. Here the algorithm tries to optimize for lower interrupt rate so an
62 and the internal state of the algorithm. The states reflect the "direction" of
63 the algorithm: is it going left (reducing moderation), right (increasing
66 algorithm would increase in order to reduce calculation overhead. Also, after
[all …]
|
| D | nexthop-group-resilient.rst | 13 algorithm, described in RFC 2992.
15 To select a next hop, hash-threshold algorithm first assigns a range of
29 under the hash-threshold algorithm.
48 constituent next hops: a hash table. The selection algorithm uses SKB hash
53 algorithm, the range of hashes associated with a next hop must be
67 under the resilient hashing algorithm.
76 Algorithm chapter
79 In a nutshell, the algorithm works as follows. Each next hop deserves a
97 After assigning wants counts to next hops, an "upkeep" algorithm runs. For
127 When offloading resilient groups, the algorithm that distributes buckets
[all …]
|
| D | dctcp.rst | 7 DCTCP is an enhancement to the TCP congestion control algorithm for data
26 The algorithm is further described in detail in the following two
|
| /Documentation/devicetree/bindings/sound/ |
| D | cs35l33.txt | 43 Optional H/G Algorithm sub-node:
46 the internal H/G Algorithm.
48 - cirrus,hg-algo : Sub-node for internal Class H/G algorithm that
53 - cirrus,mem-depth : Memory depth for the Class H/G algorithm measured in
67 algorithm uses the max detection path. If not present, the LDO
71 algorithm switches to the LDO voltage. This property can be set to values
78 - cirrus,vp-hg : Class H/G algorithm VPhg. Controls the H/G algorithm's
|
| D | cs35l35.txt | 69 Optional H/G Algorithm sub-node:
72 that will disable automatic control of the internal H/G Algorithm.
75 or using these Class H Algorithm controls over the internal Algorithm.
78 - cirrus,classh-internal-algo : Sub-node for the Internal Class H Algorithm
79 See Section 4.3 Internal Class H Algorithm in the Datasheet.
80 If not used, the device manages the ClassH Algorithm internally.
|
| /Documentation/admin-guide/blockdev/ |
| D | zram.rst | 90 3) Select compression algorithm
95 or change the selected compression algorithm (once the device is initialised
96 there is no way to change compression algorithm).
104 #select lzo compression algorithm
110 4) Set compression algorithm parameters: Optional
115 attribute which provides a per-algorithm params configuration.
120 compression algorithm to use external pre-trained dictionary, pass full
126 #same, but using algorithm priority
134 Parameters are algorithm specific: not all algorithms support pre-trained
233 comp_algorithm RW show and change the compression algorithm
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | intel,dwmac-plat.yaml | 72 snps,dcb-algorithm;
78 snps,dcb-algorithm;
89 snps,dcb-algorithm;
95 snps,dcb-algorithm;
|
| D | snps,dwmac.yaml | 222 snps,dcb-algorithm:
225 snps,avb-algorithm:
253 - snps,dcb-algorithm
256 snps,avb-algorithm: false
259 - snps,avb-algorithm
262 snps,dcb-algorithm: false
362 description: TX queue weight (if using a DCB weight algorithm)
363 snps,dcb-algorithm:
366 snps,avb-algorithm:
400 - snps,dcb-algorithm
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | stericsson,ab8500-chargalg.yaml | 8 title: AB8500 Charging Algorithm
37 charging-algorithm {
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 71 the internal-hash algorithm)
128 internal_hash:algorithm(:key) (the key is optional)
134 You can use a crc algorithm (such as crc32), then integrity target
136 You can also use a hmac algorithm (for example
148 journal_crypt:algorithm(:key) (the key is optional)
149 Encrypt the journal using given algorithm to make sure that the
160 journal_mac:algorithm(:key) (the key is optional)
163 crc algorithm, to protect against malicious modification, use a
164 hmac algorithm with a key.
|
| D | verity.rst | 17 <algorithm> <digest> <salt>
58 <algorithm>
59 The cryptographic hash algorithm used for this device. This should
60 be the name of the algorithm, like "sha1".
188 selected cryptographic digest algorithm. The hashes are linearly-ordered in
|
| /Documentation/core-api/ |
| D | genalloc.rst | 97 Allocations with gen_pool_alloc_algo() specify an algorithm to be
98 used to choose the memory to be allocated; the default algorithm can be set
100 algorithm; most ignore it, but it is occasionally needed. One can,
101 naturally, write a special-purpose algorithm, but there is a fair set
105 algorithm if none other has been specified.
|
| /Documentation/arch/arm/ |
| D | cluster-pm-race-avoidance.rst | 2 Cluster-wide Power-up/power-down race avoidance algorithm
5 This file documents the algorithm which is used to coordinate CPU and
9 The section "Rationale" explains what the algorithm is for and why it is
12 algorithm in use.
103 In this algorithm, each individual core in a multi-core processor is
109 The algorithm defines the following states for each CPU in the system:
187 race avoidance algorithm.
271 The race avoidance algorithm does not provide a way to determine
452 The race avoidance algorithm documented above does not provide a
517 As currently described and implemented, the algorithm does not
[all …]
|
| D | vlocks.rst | 27 Algorithm chapter
30 The easiest way to explain the vlocks algorithm is with some pseudo-code::
70 "entering" array in Lamport's bakery algorithm [1].
123 the basic algorithm:
172 when executing the algorithm in cached memory.
|
| /Documentation/admin-guide/ |
| D | module-signing.rst | 34 sizes 256, 384, and 512 (the algorithm is selected by data in the signature).
78 (3) :menuselection:`Which hash algorithm should modules be signed with?`
80 This presents a choice of which hash algorithm the installation phase will
92 The algorithm selected here will also be built into the kernel (rather
93 than being a module) so that modules signed with that algorithm can have
223 1. The hash algorithm (e.g., sha256)
233 The hash algorithm used does not have to match the one configured, but if it
234 doesn't, you should make sure that hash algorithm is either built into the
|
| /Documentation/RCU/ |
| D | rculist_nulls.rst | 32 1) Lookup algorithm
97 2) Insertion algorithm
120 3) Removal algorithm
159 1) lookup algorithm
195 2) Insert algorithm
|
| /Documentation/userspace-api/media/drivers/ |
| D | aspeed-video.rst | 10 options. The adopted compressing algorithm is a modified JPEG algorithm.
|
| /Documentation/networking/device_drivers/hamradio/ |
| D | baycom.rst | 114 to use the software DCD algorithm (see below)::
132 utilise a software DCD algorithm (options=1) or use a DCD signal from
137 open. It is highly recommended to use the software DCD algorithm,
141 par96 the software DCD algorithm for this type of modem is rather poor.
143 a reasonable DCD algorithm in software. Therefore, if your radio
|
| /Documentation/filesystems/ext4/ |
| D | checksums.rst | 8 The desired checksum algorithm is indicated in the superblock, though as
9 of October 2012 the only supported algorithm is crc32c. Some data
|
| /Documentation/filesystems/ |
| D | idmappings.rst | 63 straightforward algorithm to use is to apply the inverse of the first idmapping,
83 The algorithm to calculate what a given id maps to is pretty simple. First, we
199 This translation algorithm is used by the kernel in quite a few places. For
219 the algorithm::
227 This algorithm allows us to answer the question what userspace id a given
284 inverting the algorithm:
372 crossmapping algorithm we mentioned above in a previous section. First, the
496 algorithm introduced in a previous section:
507 The crossmapping algorithm fails in this case because the kernel id in the
522 algorithm introduced in a previous section:
[all …]
|