Ok, I don't get any failures when sending messages, as I'm always checking with can_send(). Otherwise, I call the event_dispatch().<div><br></div><div>But now I'm sure that messages get reordered somehow. It's difficult to send the code as it's quite involved, but I filled the code with some printf. I'm using own implemented barriers using the barrelfish message passing and I see the message handler that is in the barrier dispatching messages that were sent after the barrier reply. Then suddenly the message reply for the barrier arrives ... how can it be?</div>
<div><br></div><div>I don't know how the stub is working but is it possible that is sending a retry of a message after the following message has been sent?</div><div><br></div><div>zeus.</div><div><br><div class="gmail_quote">
El 13 de agosto de 2011 17:49, Timothy Roscoe <span dir="ltr"><<a href="mailto:troscoe@inf.ethz.ch">troscoe@inf.ethz.ch</a>></span> escribió:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Well, messages should never be lost or reordered on a UMP channel, but<br>
both sending and receiving messages can temporarily fail in a variety<br>
of ways (we push retries due to full channels, etc. back to the<br>
sender).<br>
<br>
This means that a single-threaded sender and receiver can deadlock if<br>
they're not careful about handling things like send failures due to a<br>
full channel, or the need to send acks back from the receiver.<br>
<br>
The stubs try to hide most of the functionality required for this,<br>
except for the fact that any send or recv can fail (as with Unix NBIO<br>
and select/poll).<br>
<br>
That said, you probably already know most of this :-)<br>
<br>
And, of course, there are probably bugs.<br>
<br>
-- Mothy<br>
<div><div></div><div class="h5"><br>
At Sat, 13 Aug 2011 15:08:27 +0200, Zeus Gómez Marmolejo <<a href="mailto:zeus.gomez@bsc.es">zeus.gomez@bsc.es</a>> wrote:<br>
> I'm trying to simplify the code (I'm using all gasnet and the library I<br>
> made), but whenever I get it simpler it turns out that it's working...<br>
><br>
> So I have to figure out where the problem is.<br>
><br>
><br>
> El 12 de agosto de 2011 11:43, Tim Harris (RESEARCH)<br>
> <<a href="mailto:tharris@microsoft.com">tharris@microsoft.com</a>>escribió:<br>
><br>
> > Could you post some code examples?****<br>
> ><br>
> > ** **<br>
> ><br>
> > Cheers,****<br>
> ><br>
> > ** **<br>
> ><br>
> > Tim****<br>
> ><br>
> > ** **<br>
> ><br>
> > ** **<br>
> ><br>
> > ** **<br>
> ><br>
> > *From:* Zeus Gómez Marmolejo [mailto:<a href="mailto:zeus.gomez@bsc.es">zeus.gomez@bsc.es</a>]<br>
> > *Sent:* 12 August 2011 10:42<br>
> > *To:* <a href="mailto:barrelfish-users@lists.inf.ethz.ch">barrelfish-users@lists.inf.ethz.ch</a><br>
> > *Subject:* [Barrelfish-users] Messages****<br>
> ><br>
> > ** **<br>
> ><br>
> > Hi,****<br>
> ><br>
> > ** **<br>
> ><br>
> > I'm developing a benchmark for message passing in Barrelfish, but I don't<br>
> > get it working properly. I experience some random errors. ****<br>
> ><br>
> > ** **<br>
> ><br>
> > The application is single threaded and it's using the flounder stubs to<br>
> > send messages via the UMP backend. Some of the messages get lost. Is it<br>
> > possible that they arrive in different order that they were sent? I'm not<br>
> > sure how to debug it****<br>
> ><br>
> > ** **<br>
> ><br>
> > ** **<br>
> ><br>
> > Thanks for your help!<br>
> ><br>
> > --<br>
> > Zeus Gómez Marmolejo<br>
> > Barcelona Supercomputing Center<br>
> > PhD student<br>
> > <a href="http://www.bsc.es" target="_blank">http://www.bsc.es</a><br>
> ><br>
> > ****<br>
> ><br>
><br>
><br>
><br>
> --<br>
> Zeus Gómez Marmolejo<br>
> Barcelona Supercomputing Center<br>
> PhD student<br>
> <a href="http://www.bsc.es" target="_blank">http://www.bsc.es</a><br>
><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Zeus Gómez Marmolejo<br>Barcelona Supercomputing Center<br>PhD student<br><a href="http://www.bsc.es" target="_blank">http://www.bsc.es</a><br><br>
<br>
</div>