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

[Prabal Dutta]

We've encountered a version of this problem in T1 but haven't tried to
reproduce or characterize it in T2.  When a node is sending a burst of
packets, for example during a bulk transfer, the inter-packet interval
(start-to-start) must be somewhat larger than a packet time or else
single-hop goodput suffers.  We didn't investigate this further at the
time because packets were being streamed across multiple hops and this
particular problem wasn't the bottleneck.  However, it might well be
for a store-and-forward bulk transport protocol.  I suspect the
problem was timing-sensitive handling of a packet on the receive path
as Jan suggests.

- Prabal

On 9/20/07, Jan Hauer <hauer at tkn.tu-berlin.de> wrote:
> 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