[dpdk-dev] [PATCH] eal: fix log level/type retrieving on a standard pthread

2016-05-18 Thread Thomas Monjalon
> > The functions rte_log_cur_msg_loglevel() and rte_log_cur_msg_logtype() > > return the current log level/type for the message being processed. They > > are used when implementing a user-defined logging stream. > > > > The current log levels and types were stored in a table indexed by the > > lco

[dpdk-dev] [PATCH] eal: fix log level/type retrieving on a standard pthread

2016-05-17 Thread David Marchand
On Mon, May 9, 2016 at 6:13 PM, Olivier Matz wrote: > From: Maxime Leroy > > The functions rte_log_cur_msg_loglevel() and rte_log_cur_msg_logtype() > return the current log level/type for the message being processed. They > are used when implementing a user-defined logging stream. > > The current

[dpdk-dev] [PATCH] eal: fix log level/type retrieving on a standard pthread

2016-05-12 Thread Olivier MATZ
Hi Ferruh, On 05/11/2016 06:39 PM, Ferruh Yigit wrote: > On 5/9/2016 5:13 PM, Olivier Matz wrote: >> --- a/lib/librte_eal/common/eal_common_log.c >> +++ b/lib/librte_eal/common/eal_common_log.c >> @@ -98,9 +98,10 @@ static int history_enabled = 1; >> struct log_cur_msg { >> uint32_t logleve

[dpdk-dev] [PATCH] eal: fix log level/type retrieving on a standard pthread

2016-05-11 Thread Ferruh Yigit
On 5/9/2016 5:13 PM, Olivier Matz wrote: > From: Maxime Leroy > > The functions rte_log_cur_msg_loglevel() and rte_log_cur_msg_logtype() > return the current log level/type for the message being processed. They > are used when implementing a user-defined logging stream. > > The current log level

[dpdk-dev] [PATCH] eal: fix log level/type retrieving on a standard pthread

2016-05-09 Thread Olivier Matz
From: Maxime Leroy The functions rte_log_cur_msg_loglevel() and rte_log_cur_msg_logtype() return the current log level/type for the message being processed. They are used when implementing a user-defined logging stream. The current log levels and types were stored in a table indexed by the lcore