[Olsr-dev] Poor routing performance
Wed Nov 10 17:54:19 CET 2010
On Wed, Nov 10, 2010 at 4:16 PM, Mitar <(spam-protected)> wrote:
> On Wed, Nov 10, 2010 at 3:54 PM, Markus Kittenberger
> <(spam-protected)> wrote:
> > so the os-specific code gets only one chance to do its job,.. (it might
> > immediately retry (or do whatever) before it returns, but that`s it,..)
> > one reason for this ist that it would get a bit complicated, to handle
> > failure on this level
> Not really. I use this in my code where I need something like this:
this is not the point,.
i just pointet out, that the os-specific parts of olsrd`s routing code (that
lives inside the olsr_ioctl_add_route() ), can not use any infrastructure of
the os-unspecific olsrd-core at the moment to try it later,.. (it can only
try again immediately, but not later)
and such a infrastructure will not be as trivial as your code snippet,..
(but of course it would be dooable,..)
but before thinking about this i would like to see a EAGAIN error,..
especially as there are no ioctl functions involved!
(at least in linux we have (netlink-socket based) routing code, and bsd has
a similar kernel interface (routing socket))
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Olsr-dev