On Wed, Dec 09, 2015 at 07:51:46AM -0500, Hal Rosenstock wrote: > > ipoib always uses the 0 pkey index to create the default ipoib > > interface. (see eg, update_parent_pkey) > > This is beyond IBA spec and is currently a linux convention for IPoIB. > IMO it should be changed to search for this pkey rather than assume > it's I don't think you are following. It uses pkey[0] as the pkey for ipoib, not necessarily for SA communication. Since there is no way to know what the desired pkey is for ipoib there is no possibility to search. Using pkey index is 0 a good solution since it allows the SM to configure ipoib defaults centrally. > > When operating securely the SA should place the pkey for default ipoib > > operation in pkey index 0, and place 0x7FFF in another index. I run > > alot of networks exactly like this and it works very well. > > Yes, it can run that way but more secure is without the full default > pkey. When full default pkey is in every port, the rest of the > partitioning doesn't really matter... That isn't what I said, I said the pkey for the default ipoib interface is in pkey[0], eg, the network runs with [0x8001,0x7FFF] as the pkey table. There is no 0xFFFF pkey except on SA nodes. Linux automatically creates ib0 on 0x8001 and the rest of the in-kernel stack (should?) correctly find and use 0x7FFF as the pkey to use to talk to the SA. acm should follow ipoib convention for creating it's multicast groups and setup it's default multicast group using pkey[0] Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
