Re: opensm: Add new torus routing engine: torus-2QoS
Thanks everybody. - "Jim Schutt" escreveu: > On Thu, 2010-10-28 at 09:48 -0600, Hal Rosenstock wrote: > > On Thu, Oct 28, 2010 at 11:05 AM, Jim Schutt > wrote: > > > > > > On Thu, 2010-10-28 at 07:42 -0600, Albino A. Aveleda wrote: > > >> Dear Jim, > > >> > > >> I have compiled and installed the opensm with torus-2qos. > > >> There is comment below in config file. > > >> --- > > >> # We need to tell the routing engine what directions we > > >> # want the torus coordinate directions to be, by specifing > > >> # the endpoints (switch GUID + port) of a link in each > > >> # direction. These links need to share a common switch, > > >> # which we call the torus seed. > > >> # Here we specify positive coordinate directions: > > >> xp_link 0x20 0x200019 # S_0_0_0 -> S_1_0_0 > > >> yp_link 0x20 0x25 # S_0_0_0 -> S_0_1_0 > > >> zp_link 0x20 0x21 # S_0_0_0 -> S_0_0_1 > > >> --- > > >> > > >> How do I get xp, yp and zp_link address? > > > > > > You can bring up your fabric once with some other routing > > > engine, say minhop, and run ibnetdiscover. > > > > > > > > > This will tell you the node GUIDs for all your switches. > > > > A minor clarification to the above: you don't need to run OpenSM at > > all to run ibnetdiscover to get the switch GUIDs. > > D'oh!! Thanks, Hal. > > -- Jim > > > > > -- Hal > > > > > Then you need to pick a switch to be the seed. If you > > > know that, e.g. your fabric is wired such that port 1, > > > say, connects to the switch in the direction you want to > > > be +x, look in your ibnetdiscover output to find the > > > node GUID for the switch connected to that port of your > > > seed switch. > > > > > > For maximum resiliency, pick the switch that your > > > opensm host connects to as the seed. > > > > > > -- Jim > > > > > >> > > >> Best regards, > > >> Albino > > >> > > >> - "Jim Schutt" escreveu: > > >> > > >> > > > >> > This posting > http://www.spinics.net/lists/linux-rdma/msg02967.html > > >> > has some example input for a 5x5x5 torus. > > >> > > > >> > You'll want to configure your torus (via opensm --torus_config > > >> > ) > > >> > so that the intra-NEM links are z-direction links. This will > allow > > >> > you to swap a QNEM and keep the fabric routable during the > process. > > >> > > > >> > Please look over the torus-2QoS section in > > >> > opensm/doc/current-routing.txt > > >> > to see why this is so, and to help understand why the info > > >> > in torus-2QoS.conf is required. > > >> > > > >> > > > > > > > > > -- > > > To unsubscribe from this list: send the line "unsubscribe > linux-rdma" in > > > the body of a message to majord...@vger.kernel.org > > > More majordomo info at > http://vger.kernel.org/majordomo-info.html > > > > > -- __ Albino A. Aveleda b...@nacad.ufrj.br System Engineer +55 21 2562-8080 NACAD-COPPE/UFRJ Federal University of Rio de Janeiro (UFRJ) -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: opensm: Add new torus routing engine: torus-2QoS
On Thu, 2010-10-28 at 09:48 -0600, Hal Rosenstock wrote: > On Thu, Oct 28, 2010 at 11:05 AM, Jim Schutt wrote: > > > > On Thu, 2010-10-28 at 07:42 -0600, Albino A. Aveleda wrote: > >> Dear Jim, > >> > >> I have compiled and installed the opensm with torus-2qos. > >> There is comment below in config file. > >> --- > >> # We need to tell the routing engine what directions we > >> # want the torus coordinate directions to be, by specifing > >> # the endpoints (switch GUID + port) of a link in each > >> # direction. These links need to share a common switch, > >> # which we call the torus seed. > >> # Here we specify positive coordinate directions: > >> xp_link 0x20 0x200019 # S_0_0_0 -> S_1_0_0 > >> yp_link 0x20 0x25 # S_0_0_0 -> S_0_1_0 > >> zp_link 0x20 0x21 # S_0_0_0 -> S_0_0_1 > >> --- > >> > >> How do I get xp, yp and zp_link address? > > > > You can bring up your fabric once with some other routing > > engine, say minhop, and run ibnetdiscover. > > > > > > This will tell you the node GUIDs for all your switches. > > A minor clarification to the above: you don't need to run OpenSM at > all to run ibnetdiscover to get the switch GUIDs. D'oh!! Thanks, Hal. -- Jim > > -- Hal > > > Then you need to pick a switch to be the seed. If you > > know that, e.g. your fabric is wired such that port 1, > > say, connects to the switch in the direction you want to > > be +x, look in your ibnetdiscover output to find the > > node GUID for the switch connected to that port of your > > seed switch. > > > > For maximum resiliency, pick the switch that your > > opensm host connects to as the seed. > > > > -- Jim > > > >> > >> Best regards, > >> Albino > >> > >> - "Jim Schutt" escreveu: > >> > >> > > >> > This posting http://www.spinics.net/lists/linux-rdma/msg02967.html > >> > has some example input for a 5x5x5 torus. > >> > > >> > You'll want to configure your torus (via opensm --torus_config > >> > ) > >> > so that the intra-NEM links are z-direction links. This will allow > >> > you to swap a QNEM and keep the fabric routable during the process. > >> > > >> > Please look over the torus-2QoS section in > >> > opensm/doc/current-routing.txt > >> > to see why this is so, and to help understand why the info > >> > in torus-2QoS.conf is required. > >> > > >> > > > > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in > > the body of a message to majord...@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: opensm: Add new torus routing engine: torus-2QoS
On Thu, Oct 28, 2010 at 11:05 AM, Jim Schutt wrote: > > On Thu, 2010-10-28 at 07:42 -0600, Albino A. Aveleda wrote: >> Dear Jim, >> >> I have compiled and installed the opensm with torus-2qos. >> There is comment below in config file. >> --- >> # We need to tell the routing engine what directions we >> # want the torus coordinate directions to be, by specifing >> # the endpoints (switch GUID + port) of a link in each >> # direction. These links need to share a common switch, >> # which we call the torus seed. >> # Here we specify positive coordinate directions: >> xp_link 0x20 0x200019 # S_0_0_0 -> S_1_0_0 >> yp_link 0x20 0x25 # S_0_0_0 -> S_0_1_0 >> zp_link 0x20 0x21 # S_0_0_0 -> S_0_0_1 >> --- >> >> How do I get xp, yp and zp_link address? > > You can bring up your fabric once with some other routing > engine, say minhop, and run ibnetdiscover. > > > This will tell you the node GUIDs for all your switches. A minor clarification to the above: you don't need to run OpenSM at all to run ibnetdiscover to get the switch GUIDs. -- Hal > Then you need to pick a switch to be the seed. If you > know that, e.g. your fabric is wired such that port 1, > say, connects to the switch in the direction you want to > be +x, look in your ibnetdiscover output to find the > node GUID for the switch connected to that port of your > seed switch. > > For maximum resiliency, pick the switch that your > opensm host connects to as the seed. > > -- Jim > >> >> Best regards, >> Albino >> >> - "Jim Schutt" escreveu: >> >> > >> > This posting http://www.spinics.net/lists/linux-rdma/msg02967.html >> > has some example input for a 5x5x5 torus. >> > >> > You'll want to configure your torus (via opensm --torus_config >> > ) >> > so that the intra-NEM links are z-direction links. This will allow >> > you to swap a QNEM and keep the fabric routable during the process. >> > >> > Please look over the torus-2QoS section in >> > opensm/doc/current-routing.txt >> > to see why this is so, and to help understand why the info >> > in torus-2QoS.conf is required. >> > >> > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: opensm: Add new torus routing engine: torus-2QoS
On Thu, 2010-10-28 at 07:42 -0600, Albino A. Aveleda wrote: > Dear Jim, > > I have compiled and installed the opensm with torus-2qos. > There is comment below in config file. > --- > # We need to tell the routing engine what directions we > # want the torus coordinate directions to be, by specifing > # the endpoints (switch GUID + port) of a link in each > # direction. These links need to share a common switch, > # which we call the torus seed. > # Here we specify positive coordinate directions: > xp_link 0x20 0x200019 # S_0_0_0 -> S_1_0_0 > yp_link 0x20 0x25 # S_0_0_0 -> S_0_1_0 > zp_link 0x20 0x21 # S_0_0_0 -> S_0_0_1 > --- > > How do I get xp, yp and zp_link address? You can bring up your fabric once with some other routing engine, say minhop, and run ibnetdiscover. This will tell you the node GUIDs for all your switches. Then you need to pick a switch to be the seed. If you know that, e.g. your fabric is wired such that port 1, say, connects to the switch in the direction you want to be +x, look in your ibnetdiscover output to find the node GUID for the switch connected to that port of your seed switch. For maximum resiliency, pick the switch that your opensm host connects to as the seed. -- Jim > > Best regards, > Albino > > - "Jim Schutt" escreveu: > > > > > This posting http://www.spinics.net/lists/linux-rdma/msg02967.html > > has some example input for a 5x5x5 torus. > > > > You'll want to configure your torus (via opensm --torus_config > > ) > > so that the intra-NEM links are z-direction links. This will allow > > you to swap a QNEM and keep the fabric routable during the process. > > > > Please look over the torus-2QoS section in > > opensm/doc/current-routing.txt > > to see why this is so, and to help understand why the info > > in torus-2QoS.conf is required. > > > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: opensm: Add new torus routing engine: torus-2QoS
Dear Jim, I have compiled and installed the opensm with torus-2qos. There is comment below in config file. --- # We need to tell the routing engine what directions we # want the torus coordinate directions to be, by specifing # the endpoints (switch GUID + port) of a link in each # direction. These links need to share a common switch, # which we call the torus seed. # Here we specify positive coordinate directions: xp_link 0x20 0x200019 # S_0_0_0 -> S_1_0_0 yp_link 0x20 0x25 # S_0_0_0 -> S_0_1_0 zp_link 0x20 0x21 # S_0_0_0 -> S_0_0_1 --- How do I get xp, yp and zp_link address? Best regards, Albino - "Jim Schutt" escreveu: > > This posting http://www.spinics.net/lists/linux-rdma/msg02967.html > has some example input for a 5x5x5 torus. > > You'll want to configure your torus (via opensm --torus_config > ) > so that the intra-NEM links are z-direction links. This will allow > you to swap a QNEM and keep the fabric routable during the process. > > Please look over the torus-2QoS section in > opensm/doc/current-routing.txt > to see why this is so, and to help understand why the info > in torus-2QoS.conf is required. > -- __ Albino A. Aveleda b...@nacad.ufrj.br System Engineer +55 21 2562-8080 NACAD-COPPE/UFRJ Federal University of Rio de Janeiro (UFRJ) -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 00/18] opensm: Add new torus routing engine: torus-2QoS
Hi Sasha, On Sat, 2010-09-04 at 06:15 -0600, Sasha Khapyorsky wrote: > Hi Jim, > > On 10:42 Fri 03 Sep , Jim Schutt wrote: > > This is v4 of a patchset to add to opensm a new routing engine designed > > to handle large fabrics connected with a 2D/3D torus topology. > > I've pushed this as separate branch now. So we will be able to continue > merging there, after OFED will pick up the recent management release. This is great, thanks. -- Jim > > Sasha > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v4 00/18] opensm: Add new torus routing engine: torus-2QoS
Hi Jim, On 10:42 Fri 03 Sep , Jim Schutt wrote: > This is v4 of a patchset to add to opensm a new routing engine designed > to handle large fabrics connected with a 2D/3D torus topology. I've pushed this as separate branch now. So we will be able to continue merging there, after OFED will pick up the recent management release. Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH v4 00/18] opensm: Add new torus routing engine: torus-2QoS
This is v4 of a patchset to add to opensm a new routing engine designed to handle large fabrics connected with a 2D/3D torus topology. Changes since v3: - Rebased to e5615a7039. - Simplify changes to setup_routing_engines() based on Sasha's feedback. - Bug fix: Don't install torus fabric links based on torus config, as locate_sw() does the right thing always anyway. - Bug fix: Correctly check for existence in fabric of configured seed switches. - Divide "Add torus-2QoS routing engine" patch into four parts to avoid rejection by mailing list. Changes since v2: - Rebased to a3dec3a87a. - Divide "Add torus-2QoS routing engine" patch into three parts to avoid rejection by mailing list. - Bug fix: reduce number of required seed links for a torus with one or more dimensions of radix four. - Bug fix: don't let torus-2QoS be fooled into thinking it can route a torus with two or more blocks of switches adjacent in z missing. - Bug fix: if osm_ucast_mgr_process() fails, no configured routing engine could route the fabric, so wait for a trap or sweep interval before next heavy sweep. - Bug fix: cut-n-paste error in handle_case_0x731(). Changes since initial version: - Merged my patchsets from 11/20/2009, 12/18/2009, 2/16/2010. - Moved infomation contained in the earlier patch series introduction emails into the appropriate commit messages. - Rebased to c183eb8c4c. - Addressed issues found by Yevgeny Kliteynik in original patchsets. Yevgeny's --no_default_routing option patch is not included in the merging, but would be a good addition. - Renamed osm_ucast_torus.c to osm_torus.c. Since osm_torus.c contains code to implement both unicast and multicast routing, the new name seems more appropriate. The multicast support depends heavily on the unicast routing code, so it is more convenient to keep everything in one file. - Removed redundant check for changed sl2vl map. This functionality already exists in sl2vl_update_table(). - Set sl2vl maps on CA ports for torus-2QoS. This was missing in the original patches. - Do not force torus-2QoS to use SLs 8-15 when not using "opensm -Q". This was an interim measure introduced before multicast support was working, that allowed multicast to use SL/VL 0 and thus not deadlock against unicast. I forget to take it out in the multicast patchset, so I took it out when I merged. - Renamed torus variables referencing "origin" to "seed". These things refer to switches used to seed the torus topology appropriately, so the new name should reduce confusion going forward. This also contains a keyword change in the torus configuration file, so I'll repost an updated example. Jim Schutt (18): opensm: Prepare for routing engine input to path record SL lookup and SL2VL map setup. opensm: Allow the routing engine to influence SL2VL calculations. opensm: Allow the routing engine to participate in path SL calculations. opensm: Track the minimum value in the fabric of data VLs supported. opensm: Add struct osm_routing_engine callback to build spanning trees for multicast. opensm: Make mcast_mgr_purge_tree() available outside osm_mcast_mgr.c. opensm: Add torus-2QoS routing engine, part 1. opensm: Add torus-2QoS routing engine, part 2. opensm: Add torus-2QoS routing engine, part 3. opensm: Add torus-2QoS routing engine, part 4. opensm: Update documentation to describe torus-2QoS. opensm: Enable torus-2QoS routing engine. opensm: Add opensm option to specify file name for extra torus-2QoS configuration information. opensm: Do not require -Q option for torus-2QoS routing engine. opensm: Make it possible to configure no fallback routing engine. opensm: Avoid havoc in minhop caused by torus-2QoS persistent use of osm_port_t:priv. opensm: Avoid havoc in dump_ucast_routes() caused by torus-2QoS persistent use of osm_port_t:priv. opensm: Cause status of unicast routing attempt to propogate to callers of osm_ucast_mgr_process(). opensm/doc/current-routing.txt | 269 +- opensm/include/opensm/osm_base.h | 18 + opensm/include/opensm/osm_multicast.h | 33 + opensm/include/opensm/osm_opensm.h | 29 +- opensm/include/opensm/osm_subnet.h |7 + opensm/include/opensm/osm_switch.h | 12 + opensm/include/opensm/osm_ucast_lash.h |3 - opensm/man/opensm.8.in |9 +- opensm/opensm/Makefile.am |2 +- opensm/opensm/main.c | 11 +- opensm/opensm/osm_console.c| 10 +- opensm/opensm/osm_dump.c |5 +- opensm/opensm/osm_link_mgr.c | 16 +- opensm/opensm/osm_mcast_mgr.c | 11 +- opensm/opensm/osm_opensm.c | 51 +- opensm/opensm/osm_port_info_rcv.c | 13 +- opensm/opensm/osm_qos.c| 40 +- opensm/opensm/osm_sa_path_record.c | 33 +- opensm/opensm/osm_state_mgr.c
[PATCH v3 08/17] opensm: Add new torus routing engine: torus-2QoS, part 2.
Signed-off-by: Jim Schutt --- Hmmm, I tried to break up the addition of osm_torus.c into mailing-list-size hunks, but evidently failed on this one; it doesn't seem to have made it to the list. I've attached the patch as a compressed file. Sorry. -- Jim opensm/opensm/osm_torus.c | 3993 + 1 files changed, 3993 insertions(+), 0 deletions(-) 0008-opensm-Add-torus-2QoS-routing-engine-part-2.patch.bz2 Description: application/bzip
[PATCH v3 00/17] opensm: Add new torus routing engine: torus-2QoS
This is v3 of a patchset to add to opensm a new routing engine designed to handle large fabrics connected with a 2D/3D torus topology. Changes since v2: - Rebased to a3dec3a87a. - Divide "Add torus-2QoS routing engine" patch into three parts to avoid rejection by mailing list. - Bug fix: reduce number of required seed links for a torus with one or more dimensions of radix four. - Bug fix: don't let torus-2QoS be fooled into thinking it can route a torus with two or more blocks of switches adjacent in z missing. - Bug fix: if osm_ucast_mgr_process() fails, no configured routing engine could route the fabric, so wait for a trap or sweep interval before next heavy sweep. - Bug fix: cut-n-paste error in handle_case_0x731(). Changes since initial version: - Merged my patchsets from 11/20/2009, 12/18/2009, 2/16/2010. - Moved infomation contained in the earlier patch series introduction emails into the appropriate commit messages. - Rebased to c183eb8c4c. - Addressed issues found by Yevgeny Kliteynik in original patchsets. Yevgeny's --no_default_routing option patch is not included in the merging, but would be a good addition. - Renamed osm_ucast_torus.c to osm_torus.c. Since osm_torus.c contains code to implement both unicast and multicast routing, the new name seems more appropriate. The multicast support depends heavily on the unicast routing code, so it is more convenient to keep everything in one file. - Removed redundant check for changed sl2vl map. This functionality already exists in sl2vl_update_table(). - Set sl2vl maps on CA ports for torus-2QoS. This was missing in the original patches. - Do not force torus-2QoS to use SLs 8-15 when not using "opensm -Q". This was an interim measure introduced before multicast support was working, that allowed multicast to use SL/VL 0 and thus not deadlock against unicast. I forget to take it out in the multicast patchset, so I took it out when I merged. - Renamed torus variables referencing "origin" to "seed". These things refer to switches used to seed the torus topology appropriately, so the new name should reduce confusion going forward. This also contains a keyword change in the torus configuration file, so I'll repost an updated example. Jim Schutt (17): opensm: Prepare for routing engine input to path record SL lookup and SL2VL map setup. opensm: Allow the routing engine to influence SL2VL calculations. opensm: Allow the routing engine to participate in path SL calculations. opensm: Track the minimum value in the fabric of data VLs supported. opensm: Add struct osm_routing_engine callback to build spanning trees for multicast. opensm: Make mcast_mgr_purge_tree() available outside osm_mcast_mgr.c. opensm: Add torus-2QoS routing engine, part 1. opensm: Add torus-2QoS routing engine, part 2. opensm: Add torus-2QoS routing engine, part 3. opensm: Update documentation to describe torus-2QoS. opensm: Enable torus-2QoS routing engine. opensm: Add opensm option to specify file name for extra torus-2QoS configuration information. opensm: Do not require -Q option for torus-2QoS routing engine. opensm: Make it possible to configure no fallback routing engine. opensm: Avoid havoc in minhop caused by torus-2QoS persistent use of osm_port_t:priv. opensm: Avoid havoc in dump_ucast_routes() caused by torus-2QoS persistent use of osm_port_t:priv. opensm: Cause status of unicast routing attempt to propogate to callers of osm_ucast_mgr_process(). opensm/doc/current-routing.txt | 269 +- opensm/include/opensm/osm_base.h | 18 + opensm/include/opensm/osm_multicast.h | 33 + opensm/include/opensm/osm_opensm.h | 29 +- opensm/include/opensm/osm_subnet.h |7 + opensm/include/opensm/osm_switch.h | 12 + opensm/include/opensm/osm_ucast_lash.h |3 - opensm/man/opensm.8.in |9 +- opensm/opensm/Makefile.am |2 +- opensm/opensm/main.c | 11 +- opensm/opensm/osm_console.c| 10 +- opensm/opensm/osm_dump.c |5 +- opensm/opensm/osm_link_mgr.c | 16 +- opensm/opensm/osm_mcast_mgr.c | 11 +- opensm/opensm/osm_opensm.c | 54 +- opensm/opensm/osm_port_info_rcv.c | 13 +- opensm/opensm/osm_qos.c| 40 +- opensm/opensm/osm_sa_path_record.c | 33 +- opensm/opensm/osm_state_mgr.c | 23 +- opensm/opensm/osm_subnet.c | 20 +- opensm/opensm/osm_switch.c |7 +- opensm/opensm/osm_torus.c | 9120 opensm/opensm/osm_ucast_lash.c | 11 +- opensm/opensm/osm_ucast_mgr.c | 55 +- 24 files changed, 9702 insertions(+), 109 deletions(-) create mode 100644 opensm/opensm/osm_torus.c -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
[PATCH v2 00/15] opensm: Add new torus routing engine: torus-2QoS
This is v2 of a patchset to add to opensm a new routing engine designed to handle large fabrics connected with a 2D/3D topology. Changes since initial version: - Merged my patchsets from 11/20/2009, 12/18/2009, 2/16/2010. - Moved infomation contained in the earlier patch series introduction emails into the appropriate commit messages. - Rebased to c183eb8c4c. - Addressed issues found by Yevgeny Kliteynik in original patchsets. Yevgeny's --no_default_routing option patch is not included in the merging, but would be a good addition. - Renamed osm_ucast_torus.c to osm_torus.c. Since osm_torus.c contains code to implement both unicast and multicast routing, the new name seems more appropriate. The multicast support depends heavily on the unicast routing code, so it is more convenient to keep everything in one file. - Removed redundant check for changed sl2vl map. This functionality already exists in sl2vl_update_table(). - Set sl2vl maps on CA ports for torus-2QoS. This was missing in the original patches. - Do not force torus-2QoS to use SLs 8-15 when not using "opensm -Q". This was an interim measure introduced before multicast support was working, that allowed multicast to use SL/VL 0 and thus not deadlock against unicast. I forget to take it out in the multicast patchset, so I took it out when I merged. - Renamed torus variables referencing "origin" to "seed". These things refer to switches used to seed the torus topology appropriately, so the new name should reduce confusion going forward. This also contains a keyword change in the torus configuration file, so I'll repost an updated example. Jim Schutt (15): opensm: Prepare for routing engine input to path record SL lookup and SL2VL map setup. opensm: Allow the routing engine to influence SL2VL calculations. opensm: Allow the routing engine to participate in path SL calculations. opensm: Track the minimum value in the fabric of data VLs supported. opensm: Add struct osm_routing_engine callback to build spanning trees for multicast. opensm: Make mcast_mgr_purge_tree() available outside osm_mcast_mgr.c. opensm: Add torus-2QoS routing engine. opensm: Update documentation to describe torus-2QoS. opensm: Enable torus-2QoS routing engine. opensm: Add opensm option to specify file name for extra torus-2QoS configuration information. opensm: Do not require -Q option for torus-2QoS routing engine. opensm: Make it possible to configure no fallback routing engine. opensm: Avoid havoc in minhop caused by torus-2QoS persistent use of osm_port_t:priv. opensm: Avoid havoc in dump_ucast_routes() caused by torus-2QoS persistent use of osm_port_t:priv. opensm: Cause status of unicast routing attempt to propogate to callers of osm_ucast_mgr_process(). opensm/doc/current-routing.txt | 269 +- opensm/include/opensm/osm_base.h | 18 + opensm/include/opensm/osm_multicast.h | 33 + opensm/include/opensm/osm_opensm.h | 29 +- opensm/include/opensm/osm_subnet.h |7 + opensm/include/opensm/osm_switch.h | 12 + opensm/include/opensm/osm_ucast_lash.h |3 - opensm/man/opensm.8.in |9 +- opensm/opensm/Makefile.am |2 +- opensm/opensm/main.c | 11 +- opensm/opensm/osm_console.c| 10 +- opensm/opensm/osm_dump.c |5 +- opensm/opensm/osm_link_mgr.c | 16 +- opensm/opensm/osm_mcast_mgr.c | 11 +- opensm/opensm/osm_opensm.c | 54 +- opensm/opensm/osm_port_info_rcv.c | 13 +- opensm/opensm/osm_qos.c| 40 +- opensm/opensm/osm_sa_path_record.c | 33 +- opensm/opensm/osm_state_mgr.c | 23 +- opensm/opensm/osm_subnet.c | 20 +- opensm/opensm/osm_switch.c |7 +- opensm/opensm/osm_torus.c | 9114 opensm/opensm/osm_ucast_lash.c | 11 +- opensm/opensm/osm_ucast_mgr.c | 55 +- 24 files changed, 9696 insertions(+), 109 deletions(-) create mode 100644 opensm/opensm/osm_torus.c -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
