env_dpdk: set crypto log level to ERR

This will eliminate a lot of unnecessary verbose
messages, especially from cryptodev.

Change-Id: I000adfa524c86f6379ebab4ba2087a8d6fabfe5f
Signed-off-by: paul luse <paul.e.luse@intel.com>
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/454099
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
This commit is contained in:
paul luse 2019-05-10 18:12:08 -04:00 committed by Jim Harris
parent 0d99245c13
commit 8ac86b24a2

View File

@ -306,6 +306,14 @@ spdk_build_eal_cmdline(const struct spdk_env_opts *opts)
return -1;
}
/* Lower default CRYPTO loglevel to RTE_LOG_ERR to avoid a ton of init msgs.
* This can be overridden by specifying the same option in opts->env_context
*/
args = spdk_push_arg(args, &argcount, strdup("--log-level=lib.cryptodev:5"));
if (args == NULL) {
return -1;
}
/* `user1` log type is used by rte_vhost, which prints an INFO log for each received
* vhost user message. We don't want that. The same log type is also used by a couple
* of other DPDK libs, but none of which we make use right now. If necessary, this can