[Tinyos Core WG] arbiter issues

[Kevin Klues]

The problem was only showing up in the RoundRobin arbiters.  The fix
was very simple(changing the order of two if statements), and I'm
commiting it to the developer branch now.

The problem occured when an arbiter was connected to multiple clients,
but only a single client was using the resource and it made another
request before releasing it.  The request would be queued, but the
granted event would never come back.  The loop in the implementation
of the round robin dequeing policy was stopping at the client just
before the current owner of the resource.  Extending it to include
this client allows it to operatie properly.  The problem/fix was
originally pointed out by Andres Koepke from TU Berlin

Kevin

On 10/22/06, Philip Levis <pal at cs.stanford.edu> wrote:
> The last telecon brought up a bunch of issues with the arbiters. I
> tested the cases described (request while holding) and it seemed to
> work fine. I searched through the commit archives and couldn't find
> any recent changes. Did I miss a check-in, did I misunderstand the
> bug, or did I not tickle it properly? My code was simple:
>
> boot:
>    request resource
>
> granted:
>    request resource
>
> timer:
>    release resource
>
> Phil
> _______________________________________________
> Tinyos-2.0wg mailing list
> Tinyos-2.0wg at Mail.Millennium.Berkeley.EDU
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg
>


-- 
~Kevin