From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Jens Domke <domke.j.aa@m.titech.ac.jp>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Torsten Hoefler <htor-gy3b+zu4XSAfv37vnLkPlQ@public.gmane.org>
Subject: Re: [PATCH 1/1] OpenSM: dfsssp - add support for multicast
Date: Fri, 03 May 2013 13:45:25 -0400 [thread overview]
Message-ID: <5183F7B5.3010809@dev.mellanox.co.il> (raw)
In-Reply-To: <1367496926-6824-1-git-send-email-domke.j.aa@m.titech.ac.jp>
On 5/2/2013 8:15 AM, Jens Domke wrote:
> Recent tests on a large system revealed a problem with loops in the multicast routing.
> Using DFSSSP together with the default mcast routing algorithm of OpenSM can
> produce loops in the fabric.
>
> This patch adds the mcast_build_stree function to the DFSSSP routing algorithm,
> so that DFSSSP is able to calculate the correct mcast forwarding tables for the
> subnet.
>
> It almost does the same steps as the default mcast routing, except that it
> uses the Dijkstra algorithm to generate the spanning tree instead of using the
> hop count information given by the unicast routing.
>
> General overview of the algorithm in pseudo-code:
> 1) identify the ports, which are part of the multicast group
> 2) find the 'best' switch (depending on the hop count) for the mcast group,
> which can be used as a root of the spanning tree
> 3) perform a dijkstra step with the root switch as starting point
> to generate a spanning tree to all other switches in the subnet
> 4) build the mcast forwarding tables for relevant switches:
> 4.1) select a switch which has mcast member ports connected to it
> 4.2) set the downstream ports for the mcast member ports in the mcft
> 4.3) traverse towards the root of the spanning tree and set up-/downstream
> ports on this path for all involved switches
> 4.4) goto 4.1 until all switches have been processed
>
> The same mcast algorithm will be used for SSSP, because SSSP has the potential to
> produce loops in the mcast forwarding table as well.
>
> Signed-off-by: Jens Domke <domke.j.aa@m.titech.ac.jp>
Thanks. Applied.
-- Hal
--
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
prev parent reply other threads:[~2013-05-03 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 12:15 [PATCH 1/1] OpenSM: dfsssp - add support for multicast Jens Domke
2013-05-03 17:45 ` Hal Rosenstock [this message]
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=5183F7B5.3010809@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=domke.j.aa@m.titech.ac.jp \
--cc=htor-gy3b+zu4XSAfv37vnLkPlQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox