https://oldwiki.funkfeuer.at/index.php?action=history&feed=atom&title=Miscellaneous_improvementsMiscellaneous improvements - Versionsgeschichte2026-04-04T14:10:23ZVersionsgeschichte dieser Seite in FunkFeuer WikiMediaWiki 1.22.5https://oldwiki.funkfeuer.at/index.php?title=Miscellaneous_improvements&diff=8112&oldid=prevHannes am 24. November 2007 um 13:26 Uhr2007-11-24T13:26:58Z<p></p>
<p><b>Neue Seite</b></p><div>* TU Wien lecture [http://tuwis.tuwien.ac.at/lva/tuwien/384090 "Verteilte systeme"], 20.4.2007 will present our ideas about optimizing complexity. Aaron also wants to adress more students from the TU to participate. DONE. Let's see if new participants want to join.<br />
* finalize the UML test server<br />
* try out the optimization ideas and document the speedup<br />
* more cleanups<br />
** olsrd is doing '''lots of''' <tt>malloc()</tt>s and <tt>free()</tt>s - use <tt>ltrace</tt> to see this.<br />
*** review <tt>malloc()</tt>/<tt>free()</tt> if it theys are superflous and can be implemented with buffers on the stack or just moving pointers around.<br />
*** are there very frequently <tt>malloc()</tt>ed and <tt>free()</tt>d ''struct''? Perhaps a free list can help to avoid lots of <tt>malloc()</tt>/<tt>free()</tt> handling.<br />
** we have several coding styles in there<br />
** add wrappers to hide type casts for Windows (and perhaps others). Reserve some prefix (e.g. ''x'' is used for this often as in <tt>xmalloc()</tt>, ''olsr_'' is IMHO quite long and there too many ''olsr_'' perfixed types and functions right now.)<br />
** fixup error reporting/tracing/logging<br />
** add synchronization and make the daemon multi-threading (e.g. the bmf plugin uses it right now, the httpinfo plugin could benefit from such a thing)<br />
** make the parameter parsing of the plugins more consistent (some are case-sensitive, some are not, most do not check syntax errors). ''Work in progress''<br />
** The incoming and outgoing packets are deserialized and serialized via pointers to packed ''struct''s. This is somewhat dangerous as other compilers or the same compielr for other architectures may or may not behave the same. And - '''worse''' - it misleads people to copy the same data various times around or play with pointers so no one can easily see ehat'e going on. I (Bernd) started with a more direct approach in src/lq_packet.c where we have one "unsigned char *" which walks sequentially through the incoming packet and gets the value with small inline functions into where one needs it later on - mostly some simple ''struct'' which is a normal C struct and used by the core code.<br />
** '''net_outbuffer_push()'' memcpy()es the packet from the caller supplied buffer into another buffer. Well, that's one more copy operation for every outgoinf packet.<br />
** ....</div>Hannes