cryptodev: remove XTS comment duplication

This patch removes duplicated text about AES-XTS
mode.

Signed-off-by: Damian Nowak <damianx.nowak@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
This commit is contained in:
Damian Nowak 2019-03-13 15:52:13 +01:00 committed by Akhil Goyal
parent 7d5ef3bb32
commit a76e869f66

View File

@ -1,5 +1,5 @@
/* SPDX-License-Identifier: BSD-3-Clause /* SPDX-License-Identifier: BSD-3-Clause
* Copyright(c) 2016-2017 Intel Corporation * Copyright(c) 2016-2019 Intel Corporation
*/ */
#ifndef _RTE_CRYPTO_SYM_H_ #ifndef _RTE_CRYPTO_SYM_H_
@ -124,11 +124,6 @@ struct rte_crypto_cipher_xform {
* keymask. As per RFC3711, the keymask should be padded with trailing * keymask. As per RFC3711, the keymask should be padded with trailing
* bytes to match the length of the encryption key used. * bytes to match the length of the encryption key used.
* *
* For AES-XTS mode of operation, two keys must be provided and
* key.data must point to the two keys concatenated together (Key1 ||
* Key2). The cipher key length will contain the total size of both
* keys.
*
* Cipher key length is in bytes. For AES it can be 128 bits (16 bytes), * Cipher key length is in bytes. For AES it can be 128 bits (16 bytes),
* 192 bits (24 bytes) or 256 bits (32 bytes). * 192 bits (24 bytes) or 256 bits (32 bytes).
* *
@ -140,6 +135,8 @@ struct rte_crypto_cipher_xform {
* For the AES-XTS mode of operation: * For the AES-XTS mode of operation:
* - Two keys must be provided and key.length refers to total length of * - Two keys must be provided and key.length refers to total length of
* the two keys. * the two keys.
* - key.data must point to the two keys concatenated together
* (key1 || key2).
* - Each key can be either 128 bits (16 bytes) or 256 bits (32 bytes). * - Each key can be either 128 bits (16 bytes) or 256 bits (32 bytes).
* - Both keys must have the same size. * - Both keys must have the same size.
**/ **/