[Olsr-dev] CCC-Camp07 Results

[Hannes Gredler]

On Wed, Aug 15, 2007 at 08:57:19AM +0200, Sven-Ola Tuecke wrote:
| To my interpretation, olsr_input_lq_tc() is a good candidate for further
| optimization. Every incoming LQ_TC will trigger a lot of mallocs (in this
| situation for each neighbour included in the message one malloc). After
| sending the unpacked LQ_TC through processing, the data is freed again.
| 
| Because of the protcol weaknesses regarding topology-information-spreading,
| the LQ_TC is the most frequent message you will see in meshes using the
| LQ/ETX extensions on the incoming queue.

hmm .. interesting ... i'l pick it up when doing the inplace updates ..
(just busy rewriting some of the plugins as the planned RT changes
trigger also a whole rat-tail of plugin changes :-/)

/hannes