Indigresso Wiki

Open Source Stuff for DASH7

User Tools

Site Tools


opentag:otlib:buffer

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

opentag:otlib:buffer [2012/03/08 20:24]
jpnorair created
opentag:otlib:buffer [2012/03/08 20:33] (current)
jpnorair [Queues Declare by Buffer Module]
Line 27: Line 27:
  
 Examples: A [[opentag:​platforms:​cc430|CC430F5137]] gateway implementation will often use 256+256+262+262=1036 bytes for the buffer (MSP430 has 2 byte words). ​ An [[opentag:​platforms:​stm32l1xx|STM32L151]] gateway has more SRAM and it might use 256+256+264+2296=3072 bytes for the Buffer Module. Examples: A [[opentag:​platforms:​cc430|CC430F5137]] gateway implementation will often use 256+256+262+262=1036 bytes for the buffer (MSP430 has 2 byte words). ​ An [[opentag:​platforms:​stm32l1xx|STM32L151]] gateway has more SRAM and it might use 256+256+264+2296=3072 bytes for the Buffer Module.
 +
 +=== Overlapping Dir In, Dir Out Buffers ===
 +In the common interface, the Dir In and Dir Out buffers actually overlap (they occupy the same space). ​ Thus the Dir In and Dir Out Queues may define the boundaries fluidly. ​ For example, there are circumstances where MPipe can be blocked, and thus the Dir Out Queue can use some extra buffer memory that would otherwise go unused. ​ Alternatively,​ in a system that gets plugged-in occasionally to use MPipe, but otherwise is detached and has no connection to MPipe, the Dir In buffer space will not be wasted. ​ The advantage of this method is most profound on memory limited systems like the CC430.
  
 ===== OTlib/​buffers.h ===== ===== OTlib/​buffers.h =====
opentag/otlib/buffer.txt ยท Last modified: 2012/03/08 20:33 by jpnorair