[netperf-talk] exact behaviour of generated burst traffic

[Kristijan Dragicevic]

> If the burst completes before the interval timer fires, netperf should 
> sit in a sigsuspend() call until the interval timer fires.  While it is 
> sitting in that sigsuspend() call, netperf will not be making any calls 
> to send.
> 
> That sigsuspend() call would become just a "sit and spin" call if you 
> configure netperf with --enable-spin in addition to --enable-burst.  It 
> should behave otherwise the same, but allow finer granularity on the 
> burst interval - at the expense of CPU consumption.
> 
> If the burst stuff is indeed compiled-in, and if you set the -w to 
> something obscenely large and still you get the same results, it is time 
> for debugging.  A system call trace would be one place to start - 
> perhaps sigsuspend() is returning an error that netperf is not otherwise 
> noticing.

Thank you very much. That's what I wanted to know :-)

Best regards,
Kristijan
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192