> -----Original Message----- > From: linux-rdma-owner@xxxxxxxxxxxxxxx [mailto:linux-rdma- > owner@xxxxxxxxxxxxxxx] On Behalf Of Hal Rosenstock > Sent: Wednesday, December 09, 2015 11:49 AM > > When IP addresses are used, the corresponding pkey is used. The issue this > patch is addressing is the mapping of 'hostnames' to pkeys, as show in this > ibacm_addr.cfg example: > > > > #Name device port pkey > > cst-lin0 mlx4_0 1 default > > cst-lin0-1 mlx4_0 1 default > > cst-lin0-2 mlx4_0 2 default > > > > Currently, 'default' is hard-coded to a pkey of 0xffff. The intent is to define > a better default value. Kaike has suggested this be the new default: > > > > 1. Find the first non-management full-member pkey; > > By "non-management full-member pkey", I think you mean "pkey which is > other than a full member of default (0x7fff) partition". Full-member pkey (with bit 15 set or 0x8000) other than 0xffff. > > > 2. If it fails, find pkey 0xffff; > > To me, finding pkey 0xffff is better/safer than assuming it's in index 0 > although it's likely there. > > > 3. If pkey 0xffff is not available, use the first pkey. > > > > Is there better alternative for what default should be? > > Order of 1 and 2 depends on use models for full default partition and other > partitions. Reversing 1 and 2 (full default partition first) would handle the > most common use models and handles Jason's case. Reversing 1 and 2 will cause problem for the SA node in a secure fabric: Node 1: 0x8001, 0xffff (SA node) Node 2: 0x8001, 0x7fff Node 3: 0x8001, 0x7fff In this case, Node 1 will use 0xffff while Nodes 2 and 3 will use 0x8001. Keeping the order will enable all nodes to use 0x8001 as the default, which also handles Jason's case. Kaike ��.n��������+%������w��{.n�����{���fk��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
