public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Dotan Barak <dotanba-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Anuj Kalia <anujkaliaiitd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Hari Subramoni <subramoni.1-ZbGKxL/pcrQ@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: CQEs in unreliable connection
Date: Fri, 29 Nov 2013 22:30:54 +0200	[thread overview]
Message-ID: <5298F97E.4030004@gmail.com> (raw)
In-Reply-To: <CADPSxAh1_iea41miuYpv4dzvfud3AqxCgUDsr8jUeTSrxMfVpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 29/11/2013 16:53, Anuj Kalia wrote:
> Dotan,
>
> In the example that I asked about, the 5 packets do not form one
> message - they are each individual messages. I assume this in the
> following.
>
> I now understand that packet reordering cannot happen in IB - thanks!
> Only packet loss can happen. From this, I can conclude the following
> (please correct me if I'm wrong somewhere):
>
> "If the requester sends a sequence of single packet messages: {M_1,
> M_2, ..., M_n}, then the sequence of packets at the responder will be
> {M_i1, M_i2, ..., M_ik}, where i1 < i2 < ... < ik. Which is just
> saying that messages can be lost, but not reordered."
>
> Is there a case where messages can be reordered in UC transport? i.e.
> if the requester issues an RDMA write to buf[0] followed by an RDMA
> write to buf[1], is it possible that at the responder the write to
> buf[1] is done before the write to buf[0]? I don't think that this is
> possible.
I assume that we are talking about a single QP.

The messages will be sent by the order they are sent:
the message that access buf[0] will be sent (and received by the 
receiver) before the message that access buf[1].

If you are talking about the way that the memory data is being written/seen
in the remote side. I'm throwing a wild guess here, but *maybe* your 
process can see
the new content in first buf[1] before buf[0] depends on the memory 
policy, NUMA location, etc...
(this isn't a zone that I have a lot of knowledge in, but I think that 
this may have affect).

Thanks
Dotan


>
> Thanks again. Your comments and blog have been really useful.
>
> --Anuj.
>
>

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-11-29 20:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 12:24 CQEs in unreliable connection Anuj Kalia
     [not found] ` <CADPSxAhQKoKOQVbixMXvQRpp0_h1iQCtChrF0v1UUR1cZsPZvA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-28 19:49   ` Dotan Barak
     [not found]     ` <52979E37.3080000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-11-29  1:37       ` Anuj Kalia
     [not found]         ` <CAGUk2tHz6AE6WdmJAXnAj8Q=StaZ1V75i5ho0=kmRdSqOVd==g@mail.gmail.com>
2013-11-29  3:11           ` Anuj Kalia
     [not found]             ` <CADPSxAjc-a0+icNH_MwVyCni9DkuyZvS_pcuWQ0x18mVDXWzvg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-29  5:58               ` Dotan Barak
     [not found]                 ` <52982D04.70503-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-11-29 14:53                   ` Anuj Kalia
     [not found]                     ` <CADPSxAh1_iea41miuYpv4dzvfud3AqxCgUDsr8jUeTSrxMfVpA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-29 20:30                       ` Dotan Barak [this message]
     [not found]                         ` <5298F97E.4030004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-11-29 20:50                           ` Anuj Kalia
     [not found]                             ` <CADPSxAjeU2u0nesuA=Go8WRufDcvztutR92dwuQyqgS1bcEeug-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-30  8:01                               ` Dotan Barak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5298F97E.4030004@gmail.com \
    --to=dotanba-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=anujkaliaiitd-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=subramoni.1-ZbGKxL/pcrQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox