All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Chinetti <peter.chinetti-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: When does IB Multicast drop?
Date: Tue, 24 Nov 2015 16:10:30 -0600	[thread overview]
Message-ID: <5654E056.5050608@gmail.com> (raw)

I've been reading* through the IBA spec (Release 1.3 2015-03-03), trying 
to understand IB multicast and its pitfalls.

I understand that IB multicast only supports Unreliable Datagram sends 
(10.5.2.1), and that there are neither delivery guarantees nor 
acknowledgments for UD sends. Furthermore, flow control is only 
available for Reliable Connections. I thought I saw that there was an 
ordering guarantee within a multicast group for a specific sender, but 
now I can't find that section again.

How far is the send guaranteed to propagate? What would cause the data 
to be dropped? Is it possible for an oversubscribed (e.g. a 80 Gb/s 
burst of multicast bandwidth trying to fit through a link with only 40 
Gb/s of bandwidth) link to slow down multicast data on a different 
network path, or will burst be "clipped" by dropping packets?

In testing some co-workers of mine have done we have found that when 
multicast is run in parallel over IB and Ether, the IB is occasionally 
slower, but does not seem to drop packets. This seems to suggest that 
flow control /is/ working for multicast (which would be great, as long 
as we know where the pathological cases are and avoid them).

Thank you,
Peter Chinetti

*Honestly, more like Control-F'ing for "multicast". Not super effective.
--
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

             reply	other threads:[~2015-11-24 22:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 22:10 Peter Chinetti [this message]
     [not found] ` <5654E056.5050608-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-11-24 23:08   ` When does IB Multicast drop? Anuj Kalia
     [not found]     ` <CADPSxAgifjbSP0qL5fvRt8G7-qgTY0YjdFuPnB9WKi7kkUw55Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-11-25 16:10       ` Christoph Lameter
     [not found]         ` <alpine.DEB.2.20.1511251007020.31676-wcBtFHqTun5QOdAKl3ChDw@public.gmane.org>
2015-11-25 17:10           ` Peter Chinetti
     [not found]             ` <5655EB96.2090600-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-11-25 17:23               ` Christoph Lameter
2015-11-25 16:34       ` Peter Chinetti

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=5654E056.5050608@gmail.com \
    --to=peter.chinetti-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.