subject:"\[dpdk\-dev\] \[PATCH\] eal\: add config option to enable asserts"

Re: [dpdk-dev] [PATCH] eal: add config option to enable asserts

2017-08-23 Thread Wiles, Keith

> On Aug 23, 2017, at 9:09 AM, Gaëtan Rivet wrote: > > Hi, > > On Wed, Aug 23, 2017 at 10:00:08PM +0800, Xueming Li wrote: >> Currently, enabling assertion have to set CONFIG_RTE_LOG_LEVEL to >> RTE_LOG_DEBUG. CONFIG_RTE_LOG_LEVEL is the default log level of control >> path, RTE_LOG_DP_LEVEL is

Re: [dpdk-dev] [PATCH] eal: add config option to enable asserts

2017-08-23 Thread Gaëtan Rivet

Hi, On Wed, Aug 23, 2017 at 10:00:08PM +0800, Xueming Li wrote: > Currently, enabling assertion have to set CONFIG_RTE_LOG_LEVEL to > RTE_LOG_DEBUG. CONFIG_RTE_LOG_LEVEL is the default log level of control > path, RTE_LOG_DP_LEVEL is the log level of data path. It's a little bit > hard to understa

[dpdk-dev] [PATCH] eal: add config option to enable asserts

2017-08-23 Thread Xueming Li

Currently, enabling assertion have to set CONFIG_RTE_LOG_LEVEL to RTE_LOG_DEBUG. CONFIG_RTE_LOG_LEVEL is the default log level of control path, RTE_LOG_DP_LEVEL is the log level of data path. It's a little bit hard to understand literally that assertion is decided by control path LOG_LEVEL, especia