Catlin Wrote, >That approach is certainly applicable for OpenIB as well. >The key is recognizing the need for a transition plan. >Customers have DAT Providers installed now, they >cannot synchronize getting new DAT Providers from >their suppliers with a new Linux release. This is >especially true since OpenIB does not currently >define a verbs interface that is suitable for iWARP >vendors to use. So dat_ia_openv() needs to still >support existing dat_registry logic and existing >DAT_PROVIDERs, otherwise it is breaking >existing code.
Are you talking about user-mode DAT/DAPL or kernel mode. For user-mode, the DAT registry mechanism and the dynamic loading of shared libraries seems to work OK and I see no need to change it. For kernel-mode the method for discovering RDMA (DAPL) providers, or having them register with an RDMA mid-layer should be something that fits in better with Linux. my 2 cents, woody _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
