Hi Hal, On 08:26 Mon 06 Oct , Hal Rosenstock wrote: > > > > Me too. See below. > > > >>> > Somehow it works without ibsim - so I suspect user_mad handles it. > >>> > > >>> > (Hal, could you clarify?) > >>> > >>> The kernel (user_mad/mad) does not change the requested registrations > >>> but I'm not sure I understand the question you are asking to be > >>> clarified. Is that what you're asking ? > >> > >> ibis works somehow with real stack. It registers 0x1 class only and > >> uses direct routing SMPs. Do you have any idea about why > >> (osm_vendor_idumad and/or libibumad don't help)? > > > > libibumad umad_register does not do anything that would affect this > > either. I can only conclude there must be something in ibutils that > > fixes this if it does work with the real stack. It shouldn't be too > > hard to track down where that registration for class 0x81 comes from. > > Are you sure this is the only registration and not DR class too ?
I'm not sure I understood the question. But I was about registration (or more accurate not registration) of class 0x81 by ibutils and by any lower layer up to kernel. > That's the first thing to confirm or maybe you've already confirmed > this and it wasn't clear to me in what you wrote. If so, I have a > theory about what could be occuring. It may be the case that it is an > effect of the kernel MAD layer in that a MAD agent can send any class > and when using request/response it matches on transaction ID which > contains the MAD agent. Unsolicited messages on that other class > wouldn't get through though. I just ran a simple test of this and that > appears to be the case. This could explain the phenomena. And then it seems that similar mechanism should be implemented in umad2sim. Sasha _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
