[Olsr-dev] [Olsr-users] Broadcast Packets & Windows Routin

Hannes Gredler (spam-protected)
Sat Feb 23 17:31:35 CET 2008

Henning Rogge wrote:
> 1.) we don't need to wake up the olsrd agent every x milliseconds
> (defined by pollrate).

actually we do ... b/c the timer buckets in the new timer code
are not kept sorted ... so we really need to walk the timer slot
every scheduling interval b/c we do not know what is in the slot
and if a timer is about to fire.

i have made some experiments with sorted timer trees and given
the frequent changes (read tc_edge updates) sorting timers did
cost a lot of performance.

perhaps if we can invest some time in a rewrite that leads to lower
consumption of timers (today we have roughly 2000 timers
facing a network of 400 nodes), (and roughly 1200 are not really required :-/)

after that rewrite we might pick up the idea of keeping the timer list sorted
and passing the timestamp of the first timer to select().

> 2.) olsrd can react to incoming network traffic at once, instead of
> waiting for x milliseconds, this might be useful for plugins

just for I/O purposes that makes a lot of sense to me now.


More information about the Olsr-dev mailing list