[Tinyos-devel] Re: [Tinyos Core WG] Proposal for VariableSizedQueueC component

[Jan Hauer]

I think it would be helpful to have async versions of QueueC (and
PoolC). They could ease the potential timing-problem on the receive
path when a second packet is received, before the first packet's
task-handler has finished - e.g. CC2420ReceiveP has only one buffer
for incoming packets (has this ever been an issue) ? Then, using a
common pool for the low-level components and app would allow to
utilize the memory better.

Jan

On 9/19/07, Philip Levis <pal at cs.stanford.edu> wrote:
> On Sep 19, 2007, at 11:51 AM, Kevin Klues wrote:
>
> > I was revising the implementation of printf, and wanted to use a queue
> > to store the characters coming in via calls to printf.  Bytes get
> > periodically flushed out of the queue, but only on synchrounous
> > boundaries.  Depending on the number of characters you want to print
> > in asynchronous context before printf has a chance to flush them, you
> > may want to increase the size of the buffer beyond 256 bytes.
>
> I'll admit, I was wondering (along with Om, it seems) exactly what
> needed a queue of more than 255 elements!
>
> Phil
> _______________________________________________
> Tinyos-devel mailing list
> Tinyos-devel at Millennium.Berkeley.EDU
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
>