[etherlab-users] problems with data exchange to slaves

Florian Pose fp at igh-essen.com
Sat Mar 27 20:33:30 CET 2010


On Fri, Mar 26, 2010 at 04:25:36PM -0700, dclark at mmto.org wrote:
> Hello Florian,
> 
> Saw the post on vma fault...I had just mentioned it since it concerned me.
> If you're not worried, nether am I... ;)
> 
> As to re-organizing the code as you suggest, it works fine now! I added
> some diagnostics to count how many cycles it takes for the slaves to go to
> OP, and it looks like somewhere between 25 and 100, depending on how fast
> you run the transactions, which is something I can easily live with by
> guarding my application from trying to do things until all slaves are
> detected in OP.

I suggest to use ecrt_domain_state(), which is the 'realtime' way to
check this. If the wc_state is EC_WC_COMPLETE, all process data are
exchanged, which usually is what matters in the end.

-- 
Best regards,
Florian Pose

http://etherlab.org



More information about the Etherlab-users mailing list