On Wed, Feb 01, 2023 at 05:04:41PM +0000, Giovanni Cabiddu wrote: > 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@xxxxxxxxxx> > Signed-off-by: Giovanni Cabiddu <giovanni.cabiddu@xxxxxxxxx> > Reviewed-by: Fiona Trahe <fiona.trahe@xxxxxxxxx> > --- > drivers/crypto/qat/qat_common/qat_compression.c | 2 +- > drivers/crypto/qat/qat_common/qat_crypto.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) Patch applied. Thanks. -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
