[Olsr-dev] Planned efforts on plugins

Henning Rogge (spam-protected)
Sun Feb 7 17:23:16 CET 2010

Am Sonntag 07 Februar 2010 13:59:11 schrieb Erik:
> > An alternative to a scheduler backport would be that the BMF
> > copies the necessary "nexthop" table for each target, so the
> > BMF-thread does not need to look up in the central OLSR core
> > structures. This way the waiting time for both threads could
> > be minimized (just use an atomic switch between two lists of
> > "next hop for originator" databases in the BMF).
> >
> > Henning Rogge
> That is not such a good idea. Making a copy of a table needs, of course, to
> be done in a thread-safe manner. And that would require.... again a mutex.
Maybe you can have a look at this patch. It applies to the current "tunnel" 
 and contains a backport of the development branch scheduler including an 
adaption of the BMF 1.6.2 code. I removed the pthread-code completely and 
hooked the BMF into the OLSR scheduler (with a parameter so that it should be 
independant of the polling interval).

I have not tested the BMF part of the patch, but normal operation should be 
working (tested in a small VM enviroment).

Henning Rogge
-------------- next part --------------
A non-text attachment was scrubbed...
Name: scheduler_bmf.patch.gz
Type: application/x-gzip
Size: 21139 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20100207/9678bc80/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20100207/9678bc80/attachment.sig>

More information about the Olsr-dev mailing list