/Linux-v5.4/tools/perf/scripts/perl/Perf-Trace-Util/ |
D | Context.c | 47 XSprePUSH; PUSHi((IV)RETVAL); in XS() 70 XSprePUSH; PUSHi((IV)RETVAL); in XS() 93 XSprePUSH; PUSHi((IV)RETVAL); in XS()
|
/Linux-v5.4/Documentation/admin-guide/device-mapper/ |
D | dm-crypt.rst | 17 Encryption cipher, encryption mode and Initial Vector (IV) generator. 30 format (selected by capi: prefix). The IV specification is the same 58 keys (for example IV seed) so the key contains more parts concatenated 82 The IV offset is a sector count that is added to the sector number 83 before creating the IV. 129 The <type> can be "none" if metadata is used only for persistent IV. 134 used for storing authentication tag (and persistent IV if needed). 142 IV generators will use sector number counted in <sector_size> units 145 For example, if <sector_size> is 4096 bytes, plain64 IV for the second
|
/Linux-v5.4/drivers/block/ |
D | cryptoloop.c | 98 int size, sector_t IV) in cryptoloop_transfer() argument 134 iv[0] = cpu_to_le32(IV & 0xffffffff); in cryptoloop_transfer() 144 IV++; in cryptoloop_transfer()
|
/Linux-v5.4/arch/x86/crypto/ |
D | aesni-intel_asm.S | 144 #define IV %xmm3 macro 2517 movups (IVP), IV 2538 pxor IV, STATE1 2543 movaps IN4, IV 2546 movaps IN2, IV 2568 pxor IV, STATE 2570 movaps IN, IV 2577 movups IV, (IVP) 2610 movaps IV, CTR 2642 movaps CTR, IV [all …]
|
/Linux-v5.4/drivers/crypto/chelsio/ |
D | chcr_algo.c | 74 #define IV AES_BLOCK_SIZE macro 796 chcr_req->sec_cpl.pldlen = htonl(IV + wrparam->bytes); in create_cipher_wr() 798 FILL_SEC_CPL_CIPHERSTOP_HI(0, 0, IV + 1, 0); in create_cipher_wr() 804 0, 0, IV >> 1); in create_cipher_wr() 836 temp = sizeof(struct cpl_rx_phys_dsgl) + dst_size + kctx_len + IV in create_cipher_wr() 1227 reqctx->imm = (transhdr_len + IV + req->nbytes) <= in process_cipher() 1229 bytes = IV + req->nbytes; in process_cipher() 1262 memcpy(reqctx->iv, req->info, IV); in process_cipher() 2276 reqctx->scratch_pad = reqctx->iv + IV; in chcr_aead_common_init() 2396 chcr_req->sec_cpl.pldlen = htonl(req->assoclen + IV + req->cryptlen); in create_authenc_wr() [all …]
|
/Linux-v5.4/drivers/zorro/ |
D | zorro.ids | 322 1500 Picasso IV Z2 RAM [Graphics Card] 323 1600 Picasso IV Z2 RAM [Graphics Card] 324 1700 Picasso IV Z2 [Graphics Card] 325 1800 Picasso IV Z3 [Graphics Card] 413 0100 AMax II/IV [Macintosh Emulator] 417 0600 Blizzard 1220-IV [Accelerator] 422 1100 Blizzard 1230-IV/1260 [Accelerator]
|
/Linux-v5.4/Documentation/hwmon/ |
D | w83627ehf.rst | 150 * 5 "Smart Fan IV" mode 154 SmartFan IV mode is configurable only if it was configured at system 156 SmartFan IV operational parameters can not be configured at this time, 157 and the various pwm attributes are not used in SmartFan IV mode. 160 returned when reading pwm attributes is unrelated to SmartFan IV
|
D | nct6775.rst | 150 * 5 "Smart Fan IV" mode 239 Smart Fan IV mode (5)
|
/Linux-v5.4/Documentation/crypto/ |
D | architecture.rst | 167 - ivsize: IV size in bytes 173 - geniv: IV generator (obsolete) 254 using the AEAD cipher with the automated IV generation. The shown 258 the caller may not use the AEAD cipher with a separate IV generator. In 259 this case, the caller must generate the IV. 327 encryption operation of the AEAD cipher with IV generator. 329 The SEQIV generates the IV.
|
D | api-samples.rst | 21 u8 iv[16]; /* AES-256-XTS takes a 16-byte IV */ 61 /* Initialize the IV */
|
D | userspace-if.rst | 159 should be processed for encryption or decryption. In addition, the IV is 174 - specification of the IV information marked with the flag ALG_SET_IV 218 should be processed for encryption or decryption. In addition, the IV is 233 - specification of the IV information marked with the flag ALG_SET_IV
|
/Linux-v5.4/tools/perf/Documentation/ |
D | android.txt | 68 IV. Environment settings for running perf 75 IV. Run perf
|
D | jitdump-specification.txt | 51 IV/ Record header
|
/Linux-v5.4/Documentation/media/uapi/mediactl/ |
D | media-controller.rst | 15 Part IV - Media Controller API
|
/Linux-v5.4/net/batman-adv/ |
D | Kconfig | 27 of the currently used B.A.T.M.A.N. IV protocol. The main 33 compatible to B.A.T.M.A.N. IV networks.
|
/Linux-v5.4/crypto/ |
D | Kconfig | 323 tristate "Sequence Number IV Generator" 330 This IV generator generates an IV based on a sequence number by 334 tristate "Encrypted Chain IV Generator" 340 This IV generator generates an IV based on the encryption of 494 Encrypted salt-sector initialization vector (ESSIV) is an IV 498 IV, making low entropy IV sources more suitable for block 505 ESSIV to the input IV. Note that in the aead case, it is assumed 507 template, and that the IV appears at the end of the authenticated
|
/Linux-v5.4/Documentation/i2c/busses/ |
D | i2c-ali15x3.rst | 67 * "Aladdin IV" includes the M1541 Socket 7 North bridge
|
/Linux-v5.4/Documentation/powerpc/ |
D | qe_firmware.rst | 16 IV - Microcode Programming Details 57 IV - Microcode Programming Details
|
/Linux-v5.4/Documentation/networking/ |
D | udplite.txt | 86 A detailed discussion of UDP-Lite checksum coverage options is in section IV. 109 IV) KERNEL BEHAVIOUR WITH REGARD TO THE VARIOUS SOCKET OPTIONS
|
D | netdev-features.txt | 97 Part IV: Features
|
D | net_dim.txt | 127 Part IV: Example
|
/Linux-v5.4/Documentation/filesystems/ |
D | fscrypt.rst | 278 IV. Moreover: 337 Each block's IV is set to the logical block number within the file as 340 - With CBC mode encryption, ESSIV is also used. Specifically, each IV 346 IV. Currently this is only allowed with the Adiantum encryption 354 filenames of up to 255 bytes, the same IV is used for every filename 359 nonce included in the IVs. Thus, IV reuse is limited to within a 362 With CTS-CBC, the IV reuse means that when the plaintext filenames 381 that IV reuse is not a problem as each symlink has its own inode.
|
/Linux-v5.4/Documentation/media/v4l-drivers/ |
D | bttv-cardlist.rst | 478 - Teppro TEV-560/InterVision IV-560
|
/Linux-v5.4/drivers/gpu/drm/nouveau/nvkm/engine/sec/fuc/ |
D | g98.fuc0s | 438 // init key, IV 502 // pull updated IV
|
/Linux-v5.4/fs/gfs2/ |
D | trace_gfs2.h | 23 dlm_state_name(IV), \
|