mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-15 07:04:44 +00:00
673184a2a5
GEN2 devices use a single CSR for PFVF messages, which leaves up to 10 bits of payload per single message. While such amount is sufficient for the currently defined messages, the transfer of bigger and more complex data streams from the PF to the VF requires a new mechanism that extends the protocol. This patch adds a new layer on top of the basic PFVF messaging, called Block Messages, to encapsulate up to 126 bytes of data in a single logical message across multiple PFVF messages of new types (SMALL, MEDIUM and LARGE BLOCK), including (sub)types (BLKMSG_TYPE) to carry the information about the actual Block Message. Regardless of the size, each Block Message uses a two bytes header, containing the version and size, to allow for extension while maintaining compatibility. The size and the types of Block Messages are defined as follow: - small block messages: up to 16 BLKMSG types of up to 30 bytes - medium block messages: up to 8 BLKMSG types of up to 62 bytes - large block messages: up to 4 BLKMSG types of up to 126 bytes It effectively works as reading a byte at a time from a block device and for each of these new Block Messages: - the requestor (always a VF) can either request a specific byte of the larger message, in order to retrieve the full message, or request the value of the CRC calculated for a specific message up to the provided size (to allow for messages to grow while maintaining forward compatibility) - the responder (always the PF) will either return a single data or CRC byte, along with the indication of response type (or error). This patch provides the basic infrastructure to perform the above operations, without defining any new message. As CRCs are required, this code now depends on the CRC8 module. Note: as a consequence of the Block Messages design, sending multiple PFVF messages in bursts, the interrupt rate limiting values on the PF are increased. Signed-off-by: Marco Chiappero <marco.chiappero@intel.com> Co-developed-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com> Signed-off-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com> Reviewed-by: Fiona Trahe <fiona.trahe@intel.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
97 lines
2.7 KiB
Text
97 lines
2.7 KiB
Text
# SPDX-License-Identifier: GPL-2.0-only
|
|
config CRYPTO_DEV_QAT
|
|
tristate
|
|
select CRYPTO_AEAD
|
|
select CRYPTO_AUTHENC
|
|
select CRYPTO_SKCIPHER
|
|
select CRYPTO_AKCIPHER
|
|
select CRYPTO_DH
|
|
select CRYPTO_HMAC
|
|
select CRYPTO_RSA
|
|
select CRYPTO_SHA1
|
|
select CRYPTO_SHA256
|
|
select CRYPTO_SHA512
|
|
select CRYPTO_LIB_AES
|
|
select FW_LOADER
|
|
select CRC8
|
|
|
|
config CRYPTO_DEV_QAT_DH895xCC
|
|
tristate "Support for Intel(R) DH895xCC"
|
|
depends on X86 && PCI
|
|
select CRYPTO_DEV_QAT
|
|
help
|
|
Support for Intel(R) DH895xcc with Intel(R) QuickAssist Technology
|
|
for accelerating crypto and compression workloads.
|
|
|
|
To compile this as a module, choose M here: the module
|
|
will be called qat_dh895xcc.
|
|
|
|
config CRYPTO_DEV_QAT_C3XXX
|
|
tristate "Support for Intel(R) C3XXX"
|
|
depends on X86 && PCI
|
|
select CRYPTO_DEV_QAT
|
|
help
|
|
Support for Intel(R) C3xxx with Intel(R) QuickAssist Technology
|
|
for accelerating crypto and compression workloads.
|
|
|
|
To compile this as a module, choose M here: the module
|
|
will be called qat_c3xxx.
|
|
|
|
config CRYPTO_DEV_QAT_C62X
|
|
tristate "Support for Intel(R) C62X"
|
|
depends on X86 && PCI
|
|
select CRYPTO_DEV_QAT
|
|
help
|
|
Support for Intel(R) C62x with Intel(R) QuickAssist Technology
|
|
for accelerating crypto and compression workloads.
|
|
|
|
To compile this as a module, choose M here: the module
|
|
will be called qat_c62x.
|
|
|
|
config CRYPTO_DEV_QAT_4XXX
|
|
tristate "Support for Intel(R) QAT_4XXX"
|
|
depends on X86 && PCI
|
|
select CRYPTO_DEV_QAT
|
|
help
|
|
Support for Intel(R) QuickAssist Technology QAT_4xxx
|
|
for accelerating crypto and compression workloads.
|
|
|
|
To compile this as a module, choose M here: the module
|
|
will be called qat_4xxx.
|
|
|
|
config CRYPTO_DEV_QAT_DH895xCCVF
|
|
tristate "Support for Intel(R) DH895xCC Virtual Function"
|
|
depends on X86 && PCI
|
|
select PCI_IOV
|
|
select CRYPTO_DEV_QAT
|
|
|
|
help
|
|
Support for Intel(R) DH895xcc with Intel(R) QuickAssist Technology
|
|
Virtual Function for accelerating crypto and compression workloads.
|
|
|
|
To compile this as a module, choose M here: the module
|
|
will be called qat_dh895xccvf.
|
|
|
|
config CRYPTO_DEV_QAT_C3XXXVF
|
|
tristate "Support for Intel(R) C3XXX Virtual Function"
|
|
depends on X86 && PCI
|
|
select PCI_IOV
|
|
select CRYPTO_DEV_QAT
|
|
help
|
|
Support for Intel(R) C3xxx with Intel(R) QuickAssist Technology
|
|
Virtual Function for accelerating crypto and compression workloads.
|
|
|
|
To compile this as a module, choose M here: the module
|
|
will be called qat_c3xxxvf.
|
|
|
|
config CRYPTO_DEV_QAT_C62XVF
|
|
tristate "Support for Intel(R) C62X Virtual Function"
|
|
depends on X86 && PCI
|
|
select PCI_IOV
|
|
select CRYPTO_DEV_QAT
|
|
help
|
|
Support for Intel(R) C62x with Intel(R) QuickAssist Technology
|
|
Virtual Function for accelerating crypto and compression workloads.
|
|
|
|
To compile this as a module, choose M here: the module
|
|
will be called qat_c62xvf.
|