On Thursday 19 February 2015 08:37:05 Lankswert, Patrick wrote: > There are many environments where malloc() is discouraged or verboten since > heaps can be non-deterministic when small (<2kb) as a result of heap > fragmentation. As long as I have a mandate to support the small devices, I > need contributors designs to address these issues. At this point, I do not > see a problem here.
That's an area I have little experience on... But looking at the current state of the C SDK as well as its future state with connectivity abstraction, I'm not sure we're going to run on 2 kB of overhead. If I were to design for such a target, I'd drop all abstractions, pre-allocate payload buffers and write directly to them when the user asks what to send. In other words, applications for such targets would be quite different from their big-device[1] counterparts. And remember I'm the guy who loves cross-platform, abstracted code. [1] big: with a whopping 128 kB of RAM or more! -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 173 bytes Desc: This is a digitally signed message part. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150219/fdb2c727/attachment.sig>
