[riot-devel] Network API task force

Oleg Hahm oliver.hahm at inria.fr
Fri May 8 14:38:38 CEST 2015


> That doesn't answer the question.
> A "udp_send" could in one implementation fill a pktbuf and use netapi,
> in another implementation just call the underlying send functions and
> return only when the payload has been copied into the send buffer, not
> malloc'ing extra memory. That should be abstracted from the user, but in
> a way that doesn't force a stack to use netapi/pktbuf.

I don't see the problem. In implementation A (the nameless stack) udp_send()
calls netapi_send(UDP_THREAD_PID, pointers_to(ip_header+udp_header+payload))
and in implementation B (nanonet) udp_send() calls netapi_send(active_pid,

printk(CARDNAME": Bad Craziness - sent packet while busy.\n" );
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20150508/fed0896a/attachment.sig>

More information about the devel mailing list