[dpdk-dev] [PATCH v3] rte_delay_us can be replaced with user function

2016-09-23 Thread jozma...@cisco.com
From: Jozef Martiniak When running single-core, some drivers tend to call rte_delay_us for a long time, and that is causing packet drops. To avoid this, rte_delay_us can be replaced with user-defined delay function with: void rte_delay_us_callback_register(void(*userfunc)(unsigned)); When userf

[dpdk-dev] [PATCH v3] rte_delay_us can be replaced with user function

2016-09-26 Thread jozma...@cisco.com
From: Jozef Martiniak When running single-core, some drivers tend to call rte_delay_us for a long time, and that is causing packet drops. To avoid this, rte_delay_us can be replaced with user-defined delay function with: void rte_delay_us_callback_register(void(*userfunc)(unsigned)); When userf

[dpdk-dev] [PATCH] rte_delay_us can be replaced with user function

2016-07-19 Thread jozma...@cisco.com
From: Jozef Martiniak when running single-core, some drivers tend to call rte_delay_us for a long time, and that is causing packet drops. Attached patch introduces 2 new functions: void rte_delay_us_callback_register(void(*userfunc)(unsigned)); void rte_delay_us_callback_unregister(void); First

[dpdk-dev] [PATCH] rte_delay_us can be replaced with user function

2016-07-20 Thread jozma...@cisco.com
From: Jozef Martiniak When running single-core, some drivers tend to call rte_delay_us for a long time, and that is causing packet drops. To avoid this, rte_delay_us can be replaced with user-defined delay function with: void rte_delay_us_callback_register(void(*userfunc)(unsigned)); When userf