Hi Sean, Todd,

Although I like the "replica" idea for its "query" performance boost - I 
suspect it will actually do not scale for very large
networks: Each node has to query for the entire database would cause N^2 load 
on the SA.
After any change (which do happen with higher probability on large networks) 
the SA will need to send each Report to N targets.

We already have some bad experience with large clusters SA query issues, like 
the one reported by Roland
"searching for SRP targets using PortInfo capability mask".

Eitan

Sean Hefty wrote:
- It is implemented in kernel mode
        - while user mode may help during initial debug, it will be important

for

                kernel mode ULPs such as SRP, IPoIB and SDP to also make use of
these records


Your kernel footprint is smaller than I expected, which is good.  Note that with
a MAD interface, kernel modules would still have access to any cached data.  I
also wanted to stick with usermode to allow saving the cache to disk, so that it
would be available immediately after a reboot.  (My assumption being that
changes to the network topology would be rare, so we could optimize around a
stable network design.)

As a related topic, there will be a separate SA client interface defined that
will generate SA query MADs for the user.

- Sean


_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

Reply via email to