Hi Jianfeng, Ferruh,
Thank you for spotting these issues. I'm on it, I will send a patch
to fix them asap.
Olivier
On Fri, 14 Apr 2017 16:32:57 +0100, Ferruh Yigit <ferruh.yi...@intel.com> wrote:
> Hi Olivier,
>
> On 4/4/2017 5:40 PM, Olivier Matz wrote:
> > Example of use:
> > ./app/test-pmd --log-level='pmd\.i40e.*,8'
> >
> > This enables debug logs for all dynamic logs whose type starts with
> > 'pmd.i40e'.
> >
> > Signed-off-by: Olivier Matz <olivier.m...@6wind.com>
>
> <...>
>
> > index f0ded185b..d98d56d2f 100644
> > --- a/lib/librte_eal/linuxapp/eal/eal.c
> > +++ b/lib/librte_eal/linuxapp/eal/eal.c
> > @@ -776,10 +776,8 @@ rte_eal_init(int argc, char **argv)
> >
> > thread_id = pthread_self();
> >
> > - eal_log_level_parse(argc, argv);
> > -
> > /* set log level as early as possible */
> > - rte_set_log_level(internal_config.log_level);
>
> Removing this line prevents using RTE_LOG_LEVEL config option.
>
> When there is no command line argument provided, I think it makes sense
> to use config option. Currently config option is set to INFO level but
> app shows DEBUG level logs, this is confusing.
>
> > + eal_log_level_parse(argc, argv);
> >
> > if (rte_eal_cpu_init() < 0) {
> > rte_eal_init_alert("Cannot detect lcores.");
> >
>
