Skip to contentSkip to conversation

Multicast group pre-creation for TopSpin old stack

DISCUSSION Yevgeny Kliteynik 4 participants 6 messages Sep 5, 2010 – Sep 7, 2010 3 messages not in the archive InfiniBand

lore
Share & tools
lore
#0 lore raw

Sasha,

There's a hack in the SM to deal with TopSpin's non-compliant join compmask for IPoIB v4 multicast group ff12:401b:<pkey>::1 The group is pre-defined and maintained as a well-known multicast group.

opensm/osm_prtn.c:

   232          /* workaround for TS */
   233          /* FIXME: remove this upon TS fixes */
   234          mc_rec.mgid = osm_ts_ipoib_mgid;
   235          memcpy(&mc_rec.mgid.raw[4], &pkey, sizeof(pkey));
   236          /* Scope in MCMemberRecord (if present) needs to be consistent with MGID */
   237          mc_rec.scope_state = ib_member_set_scope_state(scope, IB_MC_REC_STATE_FULL_MEMBER);
   238          ib_mgid_set_scope(&mc_rec.mgid, scope);

239
240 status = osm_mcmr_rcv_find_or_create_new_mgrp(p_sa, comp_mask, &mc_rec,
241 &p_mgrp);
242 if (p_mgrp) {
243 p_mgrp->well_known = TRUE;
244 if (!p->mgrp)
245 p->mgrp = p_mgrp;
246 }

As far as I can tell, this was added before git history. Any idea if it's still needed?

-- Yevgeny
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): 4C835DDF.6000809-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org

#2 lore raw

Hi Yevgeny,

Quoted 24 lines · Yevgeny Kliteynik

There's a hack in the SM to deal with TopSpin's non-compliant join compmask for IPoIB v4 multicast group ff12:401b:<pkey>::1 The group is pre-defined and maintained as a well-known multicast group.

opensm/osm_prtn.c:

   232          /* workaround for TS */
   233          /* FIXME: remove this upon TS fixes */
   234          mc_rec.mgid = osm_ts_ipoib_mgid;
   235          memcpy(&mc_rec.mgid.raw[4], &pkey, sizeof(pkey));
   236          /* Scope in MCMemberRecord (if present) needs to be consistent with MGID */
   237          mc_rec.scope_state = ib_member_set_scope_state(scope, IB_MC_REC_STATE_FULL_MEMBER);
   238          ib_mgid_set_scope(&mc_rec.mgid, scope);
   239
   240          status = osm_mcmr_rcv_find_or_create_new_mgrp(p_sa, comp_mask, &mc_rec,
   241                                                        &p_mgrp);
   242          if (p_mgrp) {
   243                  p_mgrp->well_known = TRUE;
   244                  if (!p->mgrp)
   245                          p->mgrp = p_mgrp;
   246          }
Quoted 2 lines

As far as I can tell, this was added before git history. Any idea if it's still needed?

I don't know, just remember that we have asked about this during partition manager development (somewhere in 2006), and have got an answer like "it is probably needed".

Personally I've never seen this used. Maybe Hal may remember more.

Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#3 lore raw
Quoted 27 lines · Sasha Khapyorsky

Hi Yevgeny,

Quoted 24 lines · Yevgeny Kliteynik

There's a hack in the SM to deal with TopSpin's non-compliant join compmask for IPoIB v4 multicast group ff12:401b:<pkey>::1 The group is pre-defined and maintained as a well-known multicast group.

opensm/osm_prtn.c:

   232          /* workaround for TS */
   233          /* FIXME: remove this upon TS fixes */
   234          mc_rec.mgid = osm_ts_ipoib_mgid;
   235          memcpy(&mc_rec.mgid.raw[4], &pkey, sizeof(pkey));
   236          /* Scope in MCMemberRecord (if present) needs to be consistent with MGID */ 237          mc_rec.scope_state = ib_member_set_scope_state(scope, IB_MC_REC_STATE_FULL_MEMBER); 238          ib_mgid_set_scope(&mc_rec.mgid, scope);
   239
   240          status = osm_mcmr_rcv_find_or_create_new_mgrp(p_sa, comp_mask, &mc_rec, 241                                                        &p_mgrp);
   242          if (p_mgrp) {
   243                  p_mgrp->well_known = TRUE;
   244                  if (!p->mgrp)
   245                          p->mgrp = p_mgrp;
   246          }

Quoted 8 lines
Quoted 2 lines

As far as I can tell, this was added before git history. Any idea if it's still needed?

I don't know, just remember that we have asked about this during partition manager development (somewhere in 2006), and have got an answer like "it is probably needed".

Personally I've never seen this used. Maybe Hal may remember more.

It's been carried forward just in case anyone was still running the old TS stack. It's always hard to determine the negative (when no one is using it any longer) (with the latest OpenSM) but it may be high time to deprecate this. Is anyone still using the old TS stack ? If so, is it used with OpenSM ?

Maybe Roland has insight into whether the old TS stack might be being used with (the latest) OpenSM.

-- Hal

Quoted 3 lines

Sasha

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): AANLkTinG2XEhJkYYf-kZGYx7h8wJnBcywMa4AS-KaVh4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org

#5 lore raw
Quoted 8 lines

It's been carried forward just in case anyone was still running the old TS stack. It's always hard to determine the negative (when no one is using it any longer) (with the latest OpenSM) but it may be high time to deprecate this. Is anyone still using the old TS stack ? If so, is it used with OpenSM ?

Maybe Roland has insight into whether the old TS stack might be being used with (the latest) OpenSM.

Seems a fairly remote possibility but on the other hand I guess I could see someone buying old Topspin equipment on ebay and wanting to use it with modern software. In any case, if carrying this workaround forward costs anything, I think it could be dropped.

- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

#7 lore raw
Quoted 6 lines · Roland Dreier
Quoted 6 lines

It's been carried forward just in case anyone was still running the old TS stack. It's always hard to determine the negative (when no one is using it any longer) (with the latest OpenSM) but it may be high time to deprecate this. Is anyone still using the old TS stack ? If so, is it used with OpenSM ?

Quoted 6 lines
Quoted 2 lines

Maybe Roland has insight into whether the old TS stack might be being used with (the latest) OpenSM.

Seems a fairly remote possibility but on the other hand I guess I could see someone buying old Topspin equipment on ebay and wanting to use it with modern software.

As far as I could understand this TS multicast group only impacts IPoIB communication between two TS stack clients. If so then it is likely that just using old Topspin switch will not activate this flow anyway. Right?

Quoted 2 lines

In any case, if carrying this workaround forward
costs anything, I think it could be dropped.

Ok, I think we can remove this then.

Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

#8 lore raw
Quoted 3 lines

As far as I could understand this TS multicast group only impacts IPoIB communication between two TS stack clients. If so then it is likely that just using old Topspin switch will not activate this flow anyway. Right?

I think it would affect IPoIB-ethernet gateway at least. And also probably in-band management of switches. But as I said I don't think it matters too much.

- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html