[riot-devel] Include folder in net / RPL restructuring

Landsmann, Martin Martin.Landsmann at haw-hamburg.de
Thu Jan 30 13:19:48 CET 2014


> routing is no layer (and forwarding isn't, either).
true. (shame on me)
> `sys/net/routing` metrics subdirectory seems the best solution ...
+1
________________________________________
Von: devel [devel-bounces at riot-os.org]" im Auftrag von "Oleg Hahm [oliver.hahm at inria.fr]
Gesendet: Donnerstag, 30. Januar 2014 12:35
An: RIOT OS kernel developers
Betreff: Re: [riot-devel] Include folder in net / RPL restructuring

Hi!

> I think Fabian meant the already existing directory
> ``sys/net/routing_layer/``.
The folder is called `sys/net/routing`, since routing is no layer (and
forwarding isn't, either).

> Though they might not be used by anything else but the routing layer, I
> think it is most clearly to put the function prototypes into
> sys/net/include/etx.h and the implementations into
> sys/net/routing_layer/etx/. In the optimal case all the other headers in
> there would be used by their respective upper or layer protocols, too, and
> experience showed that moving the implementation around later-on (e.g. to
> rename routing_layer to forwarding_layer ;-)) is heavily simplified, when
> public headers are not in those directories.
Definitely a good idea.

The question where to put the ETX implementation is difficult. You could
either vote for putting it into the routing folder (or a metrics
subdirectory), because ETX is mostly used as a metric for routing protocols.
But you could also locate it in the link_layer folder, because the current
implementation measures link layer metrics. Or we could put it into
cross_layer, because it can provide information for more than one service and
might be extended to return path metrics, too.

I think, currently `sys/net/routing` or a metrics subdirectory seems the best
solution to me.

Cheers,
Oleg
--
/* James M doesn't say fuck enough. */
        linux-2.4.3/net/core/netfilter.c


More information about the devel mailing list