Thanks Ludwig and Oleg. This was what I was looking for. I believe optimization will have to wait till the new release which should be fine for me.
Thanks and Regards, Akshay On Sunday, 14 December 2014, Oleg Hahm <oliver.h...@inria.fr> wrote: > Hi Akshay! > > > I wanted to know if the 32KB of SRAM on the SAMR21 will be > > sufficient to run the RPL ? Is there some footprint statistic that one > can > > consider when planning a probable system architecture. > > It is definitely our goal to archive support for a full featured network > stack > with RPL, 6LoWPAN (w/ support for full IPv6 MTU), and UDP within 32kB RAM > on a > 32-bit platform (such as the SAMR21). > > Currently, however, there are some issues to consider: > 1.) We're completely re-implementing the whole network stack. The new > version > will be less memory hungry. In the current (aka legacy) network stack > every layer keeps its own buffer, while the new version will make use > of a > global, shared buffer. I think the work on the new network stack will > be > completed in early Q1 2015. > 2.) The current default for RPL is the storing mode (MOP 2) with a maximum > routing table size of 128 entries. Since dynamic memory allocation for > most IoT applications is a bad choice and each entry consists of two > full > IPv6 addresses, a static array is allocated for the routing table. > Hence, > alone the routing table will consume more than 4k of RAM, if you build > a > RPL application in the default configuration. The size of the routing > table can be configured at compile time by supplying > RPL_MAX_ROUTING_ENTRIES=X. The MOP can be set in > sys/net/include/rpl/rpl_config.h > > Hope that helps. > > Cheers, > Oleg > -- > /* The HME is the biggest piece of shit I have ever seen. */ > linux-2.6.6/drivers/scsi/esp.h >
_______________________________________________ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
