So this means for a client the send queue size is one and for the forwarded
packets the send QUEUE size is FORWARD_COUNT ?

Did I get this right ? since whenever a client forwards a packet unless the
previous packet has been sent out it cannot insert its own packet in any
case right ?

Thanks,
Avinash

On 3/22/07, Philip Levis <[EMAIL PROTECTED]> wrote:

On Mar 22, 2007, at 11:41 AM, Avinash Sridharan wrote:

> I apologize for the incomplete mail ..... (hit the sent button by
> mistake)
>
> Here is my question:
>  I am using the forwarding engine from the collection tree frame
> work. I had a question on the queue sizes of the client queues and
> the forwarding queues.
>
> I checked ctpP.nc and there is variable called QUEUE_SIZE which is
> set to CLIENT_COUNT + FORWARD_COUNT, which would be 6.
>
> Does that mean that the queue size for the client and the forwarder
> would be 6. I am a bit confused with these variables and would like
> to get some advice as to which variables reflect the queue sizes
> for the client queue and the forwarder queue.
>

Ah, yeah, this is a little bit of nesC magic.

Basically, each sending client has a single reserved entry in the
queue. So a client's call to Send.send() returns FAIL iff it already
has a packet pending. CLIENT_COUNT is uniqueCount("...") where the
string is the key used to distinguish clients (I can't recall it off
the top of my head).

In addition to these queue entries, there's a forwarding queue of
size FORWARD_COUNT.

So, for example, if you have no components instantiate a
CollectionSenderC, then the queue size will be FORWARDING_COUNT.

The clients and forwarded packets share a single FIFO queue. CTP just
controls how much of the queue each can use.

Phil





--
Phd Dept. of Electrical Engineering
University of Southern California
http://www-scf.usc.edu/~asridhar
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to