[dpdk-dev] [PATCH v2 6/7] rte_sched: eliminate floating point in calculating byte clock

2015-02-17 Thread Stephen Hemminger
On Mon, 16 Feb 2015 22:44:31 + "Dumitrescu, Cristian" wrote: > Hi Stephen, > > Sorry, NACK. > > 1. Overflow issue > As you declare cycles_per_byte as uint32_t, for a CPU frequency of 2-3 GHz, > the line of code below results in overflow: > port->cycles_per_byte = (rte_get_tsc_hz()

[dpdk-dev] [PATCH v2 6/7] rte_sched: eliminate floating point in calculating byte clock

2015-02-16 Thread Dumitrescu, Cristian
.org Cc: Stephen Hemminger Subject: [dpdk-dev] [PATCH v2 6/7] rte_sched: eliminate floating point in calculating byte clock From: Stephen Hemminger <shemm...@brocade.com> The old code was doing a floating point divide for each rte_dequeue() which is very expensive. Change to using fixed

[dpdk-dev] [PATCH v2 6/7] rte_sched: eliminate floating point in calculating byte clock

2015-02-04 Thread Stephen Hemminger
From: Stephen Hemminger The old code was doing a floating point divide for each rte_dequeue() which is very expensive. Change to using fixed point scaled math instead. This improved performance from 5Gbit/sec to 10 Gbit/sec Signed-off-by: Stephen Hemminger ---