> > 1. Find the first non-management full-member pkey;
I.e. a pkey with the high-order bit set that is not 0xffff
> > 2. If it fails, find pkey 0xffff;
>
> 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.
>
> The only common case that I'm aware of where that might fall down is in
> the virtualized case. I'm not sure what policy is best there and would
> need to think about that scenario some more (and there is more
> fundamental issue with ACM in those environments).
Offline I had asked about reversing 1 and 2. The reasoning given was that ibacm could be running on a 'management' node, but needed to communicate with compute nodes.
IOW, the occurrence of a 'non-management, full member' pkey in the pkey table strongly indicates that a node is being used in a secure environment, and ibacm should prefer using that pkey over 0xffff.
Example: Compute nodes are assigned pkeys 0x8000 and 0x7fff. A node running the job scheduler has pkeys 0xffff and 0x8000 (maybe it's also the backup SA). Ibacm would need to select pkey 0x8000 for communication.
This seems like a reasonable argument to me.
- Sean
��.n��������+%������w��{.n�����{���fk��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
