On 8/9/07, Sean Hefty <[EMAIL PROTECTED]> wrote: > I'd like to propose the following change as a simple solution for handling SA > scalability problems: > > Modify the ib_sa module to support an SA LID that's separate from the SM LID. > > This concept is supported by the spec through SA redirection; however, I > propose > that we also allow the SA LID to be set manually by an administrator. > Additional details are below. > > --- > > The SA LID can be set to a local or remote LID - it doesn't matter to the > kernel. All SA MADs (PR queries, MC joins, event registration, etc.) would be > sent to that destination for processing. > Initially, I envision a user space library capable of responding to PR > queries, > but it could be expanded to respond to other types of requests. How the > library > responds to requests (forwarding them to the SM/SA, using lookup tables, etc.) > is outside the scope of the proposal.
Other than PRs, what SA requests are planned to be handled without reforwarding to the "real" SM/SA ? Is it just PRs ? Even PRs in QoS mode will be a challenge and likely be forwarded. -- Hal > - Sean > _______________________________________________ > 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 > _______________________________________________ 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
