[dpdk-dev] [PATCH] eal:Fix log messages always being printed from rte_eal_cpu_init

2015-06-08 Thread Wiles, Keith
On 6/8/15, 8:33 AM, "Wiles, Keith" wrote: > > >On 6/8/15, 6:09 AM, "Richardson, Bruce" >wrote: > >>On Sat, Jun 06, 2015 at 07:04:05PM -0500, Keith Wiles wrote: >>> The RTE_LOG(DEBUG, ...) messages in rte_eal_cpu_init() are printed >>> even when the log level on the command line was set to

[dpdk-dev] [PATCH] eal:Fix log messages always being printed from rte_eal_cpu_init

2015-06-08 Thread Wiles, Keith
On 6/8/15, 6:09 AM, "Richardson, Bruce" wrote: >On Sat, Jun 06, 2015 at 07:04:05PM -0500, Keith Wiles wrote: >> The RTE_LOG(DEBUG, ...) messages in rte_eal_cpu_init() are printed >> even when the log level on the command line was set to INFO or lower. >> >> The problem is the

[dpdk-dev] [PATCH] eal:Fix log messages always being printed from rte_eal_cpu_init

2015-06-08 Thread Bruce Richardson
On Sat, Jun 06, 2015 at 07:04:05PM -0500, Keith Wiles wrote: > The RTE_LOG(DEBUG, ...) messages in rte_eal_cpu_init() are printed > even when the log level on the command line was set to INFO or lower. > > The problem is the rte_eal_cpu_init() routine was called before > the command line args are

[dpdk-dev] [PATCH] eal:Fix log messages always being printed from rte_eal_cpu_init

2015-06-06 Thread Keith Wiles
The RTE_LOG(DEBUG, ...) messages in rte_eal_cpu_init() are printed even when the log level on the command line was set to INFO or lower. The problem is the rte_eal_cpu_init() routine was called before the command line args are scanned. Setting --log-level=7 now correctly does not print the