Home
last modified time | relevance | path

Searched refs:algorithm (Results 1 – 25 of 143) sorted by relevance

123456

/linux-3.3/crypto/
DKconfig90 tristate "Cryptographic algorithm manager"
104 tristate "Userspace cryptographic algorithm configuration"
117 algorithm registration.
143 This converts an arbitrary crypto algorithm into a parallel
144 algorithm that executes in kernel threads.
157 converts an arbitrary synchronous software crypto algorithm
158 into an asynchronous algorithm that executes in a kernel thread.
202 xoring it with a salt. This algorithm is mainly useful for CTR
212 This block cipher algorithm is required for IPSec.
221 This block cipher algorithm is required for IPSec.
[all …]
/linux-3.3/Documentation/crypto/
Dapi-intro.txt30 [algorithm api] (for registering algorithms)
32 The idea is to make the user interface and algorithm registration API
94 When submitting a new algorithm for inclusion, a mandatory requirement
189 SHA1 algorithm contributors:
192 DES algorithm contributors:
197 Blowfish algorithm contributors:
201 Twofish algorithm contributors:
205 SHA256/384/512 algorithm contributors:
210 AES algorithm contributors:
218 CAST5 algorithm contributors:
[all …]
/linux-3.3/net/mac80211/
DKconfig22 bool "PID controller based rate control algorithm" if EXPERT
25 This option enables a TX rate control algorithm for
34 This option enables the 'minstrel' TX rate control algorithm
41 This option enables the 'minstrel_ht' TX rate control algorithm
44 prompt "Default rate control algorithm"
48 This option selects the default rate control algorithm
54 bool "PID controller based rate control algorithm"
58 default rate control algorithm. You should choose
65 Select Minstrel as the default rate control algorithm.
79 comment "Some wireless drivers require a rate control algorithm"
/linux-3.3/drivers/crypto/
DKconfig26 tristate "PadLock driver for AES algorithm"
31 Use VIA PadLock for AES algorithm.
59 engine for the CryptoAPI AES algorithm.
89 tristate "SHA1 digest algorithm"
99 tristate "SHA256 digest algorithm"
109 tristate "SHA384 and SHA512 digest algorithm"
125 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
161 tristate "GHASH digest algorithm"
166 GHASH message digest algorithm for GCM (Galois/Counter Mode).
224 to offload cryptographic algorithm computation.
/linux-3.3/net/netfilter/ipvs/
DKconfig117 The robin-robin scheduling algorithm simply directs network
126 The weighted robin-robin scheduling algorithm directs network
139 The least-connection scheduling algorithm directs network
149 The weighted least-connection scheduling algorithm directs network
159 The locality-based least-connection scheduling algorithm is for
161 This algorithm usually directs packet destined for an IP address to
174 algorithm is also for destination IP load balancing. It is
191 The destination hashing scheduling algorithm assigns network
201 The source hashing scheduling algorithm assigns network
211 The shortest expected delay scheduling algorithm assigns network
[all …]
/linux-3.3/net/sched/
DKconfig50 scheduling algorithm. This algorithm classifies the waiting packets
67 packet scheduling algorithm. See
72 different properties and different algorithm.
81 (HFSC) packet scheduling algorithm.
122 packet scheduling algorithm.
133 packet scheduling algorithm.
144 packet scheduling algorithm.
155 scheduling algorithm. This queueing discipline allows the combination
167 scheduling algorithm.
178 (GRED) packet scheduling algorithm for some of your network devices
[all …]
/linux-3.3/drivers/i2c/algos/
DKconfig2 # I2C algorithm drivers configuration
/linux-3.3/Documentation/networking/
Dbaycom.txt104 the software DCD algorithm (see below).
121 utilise a software DCD algorithm (options=1) or use a DCD signal from
125 open. It is highly recommended to use the software DCD algorithm,
129 par96: the software DCD algorithm for this type of modem is rather poor.
131 a reasonable DCD algorithm in software. Therefore, if your radio
Dpolicy-routing.txt64 Lookup algorithm
97 Very clean, stable and robust algorithm for OSPF routing
127 It is a funny, but pretty useless algorithm.
Dfib_trie.txt31 Note that the search algorithm will simply skip over these bits when
69 level compression algorithm on part of the trie.
72 Looks up a key, deletes it and runs the level compression algorithm.
/linux-3.3/arch/xtensa/lib/
Dmemset.S121 bbci.l a5, 1, .L0 # if now aligned, return to main algorithm
128 j .L0 # dst is now aligned, return to main algorithm
Dmemcopy.S130 # return to main algorithm
141 j .Ldstaligned # dst is now aligned, return to main algorithm
/linux-3.3/Documentation/frv/
Datomic-ops.txt26 To get around this, the following algorithm has been implemented. It operates in a way similar to
34 (*) All atomic operations can then be broken down into the following algorithm:
56 This algorithm suffers from two problems:
/linux-3.3/fs/isofs/
Drock.h78 char algorithm[2]; member
Drock.c516 algo = isonum_721(rr->u.ZF.algorithm); in parse_rock_ridge_inode_internal()
549 rr->u.ZF.algorithm[0], in parse_rock_ridge_inode_internal()
550 rr->u.ZF.algorithm[1]); in parse_rock_ridge_inode_internal()
/linux-3.3/usr/
DKconfig96 This option decides by which algorithm the builtin initramfs
146 The most recent compression algorithm.
155 XZ uses the LZMA2 algorithm. The initramfs size is about 30%
/linux-3.3/drivers/net/wireless/b43/
Dmain.c796 u8 index, u8 algorithm, const u8 *key) in key_write() argument
805 value = ((kidx << 4) | algorithm); in key_write()
933 u8 index, u8 algorithm, in do_key_write() argument
947 if (algorithm == B43_SEC_ALGO_TKIP) { in do_key_write()
962 key_write(dev, index, algorithm, buf); in do_key_write()
966 dev->key[index].algorithm = algorithm; in do_key_write()
970 int index, u8 algorithm, in b43_key_write() argument
985 if (algorithm == B43_SEC_ALGO_TKIP && key_len == 32) in b43_key_write()
1016 do_key_write(dev, index, algorithm, key, key_len, mac_addr); in b43_key_write()
1020 do_key_write(dev, index + 4, algorithm, key, key_len, NULL); in b43_key_write()
[all …]
/linux-3.3/drivers/i2c/
DKconfig67 Some I2C bus drivers require so-called "I2C algorithm" modules
100 Say Y here if you want the I2C algorithm drivers to produce a bunch
/linux-3.3/lib/
DKconfig97 algorithm. Module will be called crc8.
289 tristate "CORDIC algorithm"
291 This option provides an implementation of the CORDIC algorithm;
/linux-3.3/lib/xz/
DKconfig5 LZMA2 compression algorithm and BCJ filters are supported using
/linux-3.3/Documentation/filesystems/pohmelfs/
Dinfo.txt58 with appropriate hash algorithm and key file and cipher algorithm, mode and key file:
/linux-3.3/drivers/staging/rtl8712/
Drtl871x_cmd.h205 u8 algorithm; /* encryption algorithm, could be none, wep40, member
221 u8 algorithm; member
/linux-3.3/net/bridge/
DKconfig15 networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
/linux-3.3/drivers/crypto/caam/
DKconfig61 tristate "Register algorithm implementations with the Crypto API"
/linux-3.3/drivers/md/
Draid5.h367 int level, algorithm; member

123456