Re: more network performance info: ether_output()

2012-05-01 Thread George Neville-Neil
On Apr 20, 2012, at 15:03 , Luigi Rizzo wrote: Continuing my profiling on network performance, another place were we waste a lot of time is if_ethersubr.c::ether_output() In particular, from the beginning of ether_output() to the final call to ether_output_frame() the code takes slightly

Re: more network performance info: ether_output()

2012-05-01 Thread Luigi Rizzo
On Tue, May 01, 2012 at 10:27:42AM -0400, George Neville-Neil wrote: On Apr 20, 2012, at 15:03 , Luigi Rizzo wrote: Continuing my profiling on network performance, another place were we waste a lot of time is if_ethersubr.c::ether_output() In particular, from the beginning of

Re: more network performance info: ether_output()

2012-05-01 Thread George Neville-Neil
On May 1, 2012, at 11:40 , Luigi Rizzo wrote: On Tue, May 01, 2012 at 10:27:42AM -0400, George Neville-Neil wrote: On Apr 20, 2012, at 15:03 , Luigi Rizzo wrote: Continuing my profiling on network performance, another place were we waste a lot of time is if_ethersubr.c::ether_output()

Re: more network performance info: ether_output()

2012-05-01 Thread Bjoern A. Zeeb
On 1. May 2012, at 15:40 , Luigi Rizzo wrote: On Tue, May 01, 2012 at 10:27:42AM -0400, George Neville-Neil wrote: On Apr 20, 2012, at 15:03 , Luigi Rizzo wrote: Continuing my profiling on network performance, another place were we waste a lot of time is if_ethersubr.c::ether_output()

Re: more network performance info: ether_output()

2012-05-01 Thread Luigi Rizzo
On Tue, May 01, 2012 at 09:09:05PM +, Bjoern A. Zeeb wrote: On 1. May 2012, at 15:40 , Luigi Rizzo wrote: On Tue, May 01, 2012 at 10:27:42AM -0400, George Neville-Neil wrote: ... Also, how are you doing the measurements. The measurements are done with tools/tools/netrate/netsend

more network performance info: ether_output()

2012-04-20 Thread Luigi Rizzo
Continuing my profiling on network performance, another place were we waste a lot of time is if_ethersubr.c::ether_output() In particular, from the beginning of ether_output() to the final call to ether_output_frame() the code takes slightly more than 210ns on my i7-870 CPU running at 2.93 GHz +