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

2016-09-26 Thread Thomas Monjalon
2016-09-26 10:35, jozmarti at 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_

[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 v3] rte_delay_us can be replaced with user function

2016-09-23 Thread Thomas Monjalon
2016-09-23 08:39, jozmarti at cisco.com: > --- a/lib/librte_eal/common/include/generic/rte_cycles.h > +++ b/lib/librte_eal/common/include/generic/rte_cycles.h > @@ -180,15 +180,17 @@ rte_get_timer_hz(void) > default: rte_panic("Invalid timer source specified\n"); > } > } > - > /** > +

[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