diff options
author | 2023-02-01 17:04:41 +0000 | |
---|---|---|
committer | 2023-02-10 17:20:19 +0800 | |
commit | 0ceb587dbb94e13bb70988872f1fc0cf412f5f87 (patch) | |
tree | 3eefcec647dfa4001b1a8cef9faafe7f6b118b49 /crypto/testmgr.c | |
parent | crypto: qat - fix out-of-bounds read (diff) | |
download | wireguard-linux-0ceb587dbb94e13bb70988872f1fc0cf412f5f87.tar.xz wireguard-linux-0ceb587dbb94e13bb70988872f1fc0cf412f5f87.zip |
crypto: qat - drop log level of msg in get_instance_node()
The functions qat_crypto_get_instance_node() and
qat_compression_get_instance_node() allow to get a QAT instance (ring
pair) on a device close to the node specified as input parameter.
When this is not possible, and a QAT device is available in the system,
these function return an instance on a remote node and they print a
message reporting that it is not possible to find a device on the specified
node. This is interpreted by people as an error rather than an info.
The print "Could not find a device on node" indicates that a kernel
application is running on a core in a socket that does not have a QAT
device directly attached to it and performance might suffer.
Due to the nature of the message, this can be considered as a debug
message, therefore drop the severity to debug and report it only once
to avoid flooding.
Suggested-by: Vladis Dronov <vdronov@redhat.com>
Signed-off-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Reviewed-by: Fiona Trahe <fiona.trahe@intel.com>
Reviewed-by: Vladis Dronov <vdronov@redhat.com>
Tested-by: Vladis Dronov <vdronov@redhat.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/testmgr.c')
0 files changed, 0 insertions, 0 deletions