By providing this mechanism, ib_usa provides a convenient and useful way for user applications to detect when nodes enter or leave the fabric. This is useful for fabric monitoring applications (like a system admin dashboard) or, conceivably, to allow a job scheduler to react to problems and to dynamically balance the computational load across the fabric.
As a reminder - the original proposal also supported allowing user applications to join multicast groups, but there was talk about adding that to rdma_cm, instead. -----Original Message----- From: Hefty, Sean [mailto:[email protected]] Sent: Wednesday, October 13, 2010 11:59 AM To: Mike Heinz; [email protected]; [email protected] Cc: [email protected]; Roland Dreier Subject: RE: user SA notifications, redux > As I mentioned earlier, the reason ib_sa acts as a single access point for > SA/SM traps and notices is because traps and notices are sent to ports, not > to > queue pairs and not to processes. That means only one entity can be > subscribed > for notices and traps at any particular time, and must manage them, > "sharing > them out" among all processes that are interested in them. Can you provide a brief description of the intended usage model? _______________________________________________ ewg mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg
