From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] The use of --log-level and its default state
Date: Fri, 05 Jun 2015 12:00:30 +0200 [thread overview]
Message-ID: <4143606.5Er6ccdYXp@xps13> (raw)
In-Reply-To: <D18B48A1.2100B%keith.wiles@intel.com>
2015-05-27 15:10, Wiles, Keith:
> I would like to have the log-level default changed to not log everything,
> but the user needs to enable the log messages if he needs to see more
> information. Normally applications or systems are not so verbose, but if
> needed the user enables the verbose or debug messages.
>
> Can we change the default logs and messages to be non-verbose instead?
Do you mean changing this line?
/* default value from build option */
internal_cfg->log_level = RTE_LOG_LEVEL;
It means using the most verbose level available in the build.
Maybe we should set RTE_LOG_NOTICE or RTE_LOG_WARNING,
However, there is already --log-level for the user and rte_set_log_level()
for the application developper.
So this default log level is only used for DPDK trials and development.
Probably that being verbose is a good option for such cases?
next prev parent reply other threads:[~2015-06-05 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 15:10 Wiles, Keith
2015-06-05 10:00 ` Thomas Monjalon [this message]
2015-06-05 12:32 ` Wiles, Keith
2015-06-05 13:58 ` Thomas Monjalon
2015-06-05 14:17 ` Wiles, Keith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4143606.5Er6ccdYXp@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).