[dpdk-dev] [PATCH 3/5] bnx2x: Add RTE_LIBRTE_BNX2X_REG_ACCESS config option

[Harish Patil]

>
>2015-09-11 17:42, Rasesh Mody:
>> From: Harish Patil <harish.patil at qlogic.com>
>> --- a/config/common_linuxapp
>> +++ b/config/common_linuxapp
>> @@ -220,6 +220,7 @@ CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=n
>>  CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=n
>>  CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX=n
>>  CONFIG_RTE_LIBRTE_BNX2X_MF_SUPPORT=n
>> +CONFIG_RTE_LIBRTE_BNX2X_REG_ACCESS=n
>
>Why do you need this option?

Currently logging of register accesses is using (wrongly) the generic
driver debug option of PMD_DRV_LOG (which gets enabled if
CONFIG_RTE_LIBRTE_BNX2X_DEBUG=y).
This floods the console due to excessive printing of register
reads/writes. So creating a new debug option in order to capture only the
register read/writes (if required) and also does not interfere with the
informational/user-level debug.


>Why only for Linux?
It was added for BSD as well in the subsequent patch ([PATCH 1/6] bnx2x:
FreeBSD enablement). Will include it in a single patch in v2 series.

>And last but not the least, why nobody else have reviewed carefully this
>patch
>after one month?
>
>



________________________________

This message and any attached documents contain information from the sending company or its parent company(s), subsidiaries, divisions or branch offices that may be confidential. If you are not the intended recipient, you may not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.