numam-dpdk/lib/librte_jobstats/rte_jobstats_version.map

DPDK_2.0 {
	global:

	rte_jobstats_context_finish;
	rte_jobstats_context_init;
	rte_jobstats_context_reset;
	rte_jobstats_context_start;
	rte_jobstats_finish;
	rte_jobstats_init;
	rte_jobstats_reset;
	rte_jobstats_set_max;
	rte_jobstats_set_min;
	rte_jobstats_set_period;
	rte_jobstats_set_target;
	rte_jobstats_set_update_period_function;
	rte_jobstats_start;

	local: *;
};

DPDK_16.04 {
	global:

	rte_jobstats_abort;

} DPDK_2.0;
jobstats: new library This library provide API to measure time spend in particular parts of code and to calculate optimal polling time. To calculate a those statistics application code need to be divided into parts (called jobs) that do something. It is up to application to decide what is considered a job. Series of jobs must be surrounded with the rte_jobstats_context_start() and rte_jobstats_context_finish() calls. After that, jobs might be started. Each job must be surrounded with rte_jobstats_start() and rte_jobstats_finish() calls. After job finishes its execution, period in which it should be called again is adjusted. It might be used to minimize time wasted on unnecessary polls/calls. Adjustment is based on data provided by job itself (ex: number of packets it processed). After all jobs in serie are executed fallowing statistics are updated and might be used by application. Statistics can be reset. Some of provided statistic data: - total/min/max execution - time spent in executing jobs. - total/min/max management - time spent outside execution area. This value might be used to measure overhead of scheduling jobs. This time also contains overhead of rte_jobstats library itself. - number of loops that executed at least one job - executed jobs - time when statistics were reset. Each job provide total/min/max execution time and execution count statistics. Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> 2015-02-24 16:33:23 +00:00			`DPDK_2.0 {`
			`global:`

			`rte_jobstats_context_finish;`
			`rte_jobstats_context_init;`
			`rte_jobstats_context_reset;`
			`rte_jobstats_context_start;`
			`rte_jobstats_finish;`
			`rte_jobstats_init;`
			`rte_jobstats_reset;`
			`rte_jobstats_set_max;`
			`rte_jobstats_set_min;`
			`rte_jobstats_set_period;`
			`rte_jobstats_set_target;`
			`rte_jobstats_set_update_period_function;`
			`rte_jobstats_start;`

			`local: *;`
			`};`
jobstats: add abort function This patch adds new function rte_jobstats_abort. It marks job as finished and time of this work will be add to management time instead of execution time. This function should be used instead of rte_jobstats_finish if condition occurs, condition is defined by the application for example when receiving n>0 packets. Example of usage is added to the example l2fwd-jobstats. At maximum load do-while loop inside Idle job will be execute once because one or more jobs waiting to be executed, so this time should not be include as the execution time by calling rte_jobstats_abort(). Signed-off-by: Marcin Kerlin <marcinx.kerlin@intel.com> Acked-by: Fan Zhang <roy.fan.zhang@intel.com> 2016-02-12 16:04:41 +00:00
			`DPDK_16.04 {`
			`global:`

			`rte_jobstats_abort;`

			`} DPDK_2.0;`