Hey Flavio,
Here is the detailed root cause: For revalidator threads, there is one leader thread that calls poll_block() regularly. Other Non-leader threads do not call poll_block() in their main loop, and instead synchronizes with leader thread by waiting on the barrier. However, non-leader revalidators could call poll_block() in nl_sock_recv__() due to block on reading flow dump from kernel. This can happen fairly frequently when there are very few flows. The execution of poll_block() will check the last_wakeup time, and calculate the poll interval (time_msec() - last_wakeup). if the poll interval is greater than 1000 ms, a warning you reported is issued. Sorry for the confusion, this should be fixed. We'll discuss a solution and post a fix soon. Thanks, Alex Wang, On Wed, May 28, 2014 at 3:29 PM, Flavio Leitner <[email protected]> wrote: > I am seeing this message > timeval(revalidator13)|WARN|Unreasonably long 16518ms poll interval (634ms > user, 395ms system) > > while running from the current master branch: > 8cc8680 lib/flow: call memcmp in miniflow_equal() > > Any suggestion what could be or how to debug this further? > fbl > > _______________________________________________ > dev mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/dev >
_______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
