Wow! volatile...and cogent descriptions of TOS tasks and Spin Lock usage...
You guys are gods!
MS
ps...in the original code, you probably don't really need the atomics
(or the intermediate "tb" because the "blocking" value is a single
byte and the test is only going one way, which is (I think, under
all conditions) going to be reliably TRUE or FALSE from instruction
to instruction...
R. Steve McKown wrote:
On Thursday 07 December 2006 03:10 pm, Philip Levis wrote:
On Dec 7, 2006, at 12:51 PM, R. Steve McKown wrote:
I think in general the need/desire for a spin lock or other similar
continue-to-test strategies suggest that some of the best benefits
of TinyOS
aren't being fully exploited.
This is generally true. There are situations, though, when small spin
loops can improve performance. This happens when the spinning time is
shorter than the time to execute the prelude for the corresponding
interrupt handler
Thanks for this post, Phil. It's just this kind of knowledge sharing that
makes tinyos-help such a value and joy to participate in!
All the best,
Steve
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
