From: Stephen Hemminger <stephen@networkplumber.org>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: dev@dpdk.org
Subject: Re: [PATCH 2/6] rte_log.h: add detailed log levels RTE_LOG{FINE, FINER, FINEST}
Date: Fri, 13 Nov 2015 08:07:41 -0800 [thread overview]
Message-ID: <20151113080741.1ed783d0@xeon-e3> (raw)
In-Reply-To: <1447397258-27233-3-git-send-email-mhall@mhcomputing.net>
On Fri, 13 Nov 2015 06:47:34 +0000
Matthew Hall <mhall@mhcomputing.net> wrote:
> Signed-off-by: Matthew Hall <mhall@mhcomputing.net>
> ---
> lib/librte_eal/common/include/rte_log.h | 19 +++++++++++--------
> 1 file changed, 11 insertions(+), 8 deletions(-)
>
> diff --git a/lib/librte_eal/common/include/rte_log.h b/lib/librte_eal/common/include/rte_log.h
> index 9dad24e..7dc19e1 100644
> --- a/lib/librte_eal/common/include/rte_log.h
> +++ b/lib/librte_eal/common/include/rte_log.h
> @@ -90,14 +90,17 @@ extern struct rte_logs rte_logs;
> #define RTE_LOGTYPE_USER8 0x80000000 /**< User-defined log type 8. */
>
> /* Can't use 0, as it gives compiler warnings */
> -#define RTE_LOG_EMERG 1U /**< System is unusable. */
> -#define RTE_LOG_ALERT 2U /**< Action must be taken immediately. */
> -#define RTE_LOG_CRIT 3U /**< Critical conditions. */
> -#define RTE_LOG_ERR 4U /**< Error conditions. */
> -#define RTE_LOG_WARNING 5U /**< Warning conditions. */
> -#define RTE_LOG_NOTICE 6U /**< Normal but significant condition. */
> -#define RTE_LOG_INFO 7U /**< Informational. */
> -#define RTE_LOG_DEBUG 8U /**< Debug-level messages. */
> +#define RTE_LOG_EMERG 1U /**< System is unusable. */
> +#define RTE_LOG_ALERT 2U /**< Action must be taken immediately. */
> +#define RTE_LOG_CRIT 3U /**< Critical conditions. */
> +#define RTE_LOG_ERR 4U /**< Error conditions. */
> +#define RTE_LOG_WARNING 5U /**< Warning conditions. */
> +#define RTE_LOG_NOTICE 6U /**< Normal but significant condition. */
> +#define RTE_LOG_INFO 7U /**< Informational. */
> +#define RTE_LOG_DEBUG 8U /**< Debug-level messages. */
> +#define RTE_LOG_FINE 9U /**< Fine-level messages. */
> +#define RTE_LOG_FINER 10U /**< Finer-level messages. */
> +#define RTE_LOG_FINEST 11U /**< Finest-level messages. */
>
> /** The default log stream. */
> extern FILE *eal_default_log_stream;
I understand the motivation but the existing levels match syslog
which are what you want for a production application.
The new levels are only for developer logs. I don't think we want all
the developer levels beyond debug in the upstream tree anyway.
next prev parent reply other threads:[~2015-11-13 16:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 6:47 [PATCH 0/6] librte_eal: allow wider range of log levels Matthew Hall
2015-11-13 6:47 ` [PATCH 1/6] librte_log: add function to retrieve log_level Matthew Hall
2015-11-13 11:40 ` Bruce Richardson
2015-11-13 11:49 ` Thomas Monjalon
2015-11-13 19:04 ` Matthew Hall
2015-11-13 19:01 ` Matthew Hall
2015-11-13 6:47 ` [PATCH 2/6] rte_log.h: add detailed log levels RTE_LOG{FINE, FINER, FINEST} Matthew Hall
2015-11-13 11:44 ` Bruce Richardson
2015-11-13 11:48 ` Ananyev, Konstantin
2015-11-13 19:14 ` Matthew Hall
2015-11-13 19:16 ` Matthew Hall
2015-11-13 16:07 ` Stephen Hemminger [this message]
2015-11-13 19:15 ` Matthew Hall
2015-11-13 6:47 ` [PATCH 3/6] eal_common_log.c: reset default level to RTE_LOG_FINEST Matthew Hall
2015-11-13 6:47 ` [PATCH 4/6] rte_log.h: update logging docs to include FINEST level Matthew Hall
2015-11-13 6:47 ` [PATCH 5/6] rte_log.h: add RTE_SYSLOG_LEVEL_MAX Matthew Hall
2015-11-13 6:47 ` [PATCH 6/6] eal_log.c: limit syslog level to RTE_SYSLOG_LEVEL_MAX Matthew Hall
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=20151113080741.1ed783d0@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.