[dpdk-dev] [PATCH v3] pipeline: add statistics for librte_pipeline

Thomas Monjalon thomas.monjalon at 6wind.com
Fri Jun 5 12:30:35 CEST 2015


2015-05-28 19:26, Dumitrescu, Cristian:
> I think we have the following options identified so far for stats collection configuration:
> 
> 1. Stats configuration through the RTE_LOG_LEVEL
> 2. Single configuration flag global for all DPDK libraries
> 3. Single configuration flag per DPDK library
> 
> It would be good if Thomas and Stephen, as well as others, would reply with their preference order.

There are important design questions in these threads.
I think that the best way to come to a conclusion is to submit a design rule
	- to state whether statistics must be considered as a feature or as debug,
	- and to decide whether stats must be always available or disabled
globally or per-library.
It should be written in a new doc. I suggest docs/guidelines/design.rst.
Then we'll have to discuss and vote on this base. It will avoid future
discussions.
The underlying discussion is to decide if every cycle is important even if
there is a real usability drawback.

In order to reach a conclusion, it seems reasonnable to target a consensus
2 weeks after the first submission of these design rules.
Thanks Cristian to follow up.


More information about the dev mailing list