[openib-general] IPoIB interface for unauthorized partition

[Eitan Zahavi]

Hi Roland, Hal,

Regarding the usage of P_Key values in setting up IPoIB interfaces:

I thought the intent of the IB spec when defining P_Key index usage (and not P_Key value) was
that the P_Key values would never need to be known above the driver level.
To avoid exposing the P_Key values we could use P_Key index for creating the IPoIB interfaces.

Does it make sense to work on a patch that would setup IPoIB interfaces by the P_Key index (and not by
P_Key value)?

Also I think the expected behavior for IPoIB should be that IPoIB "child" interfaces should be "automatically"
initialized by the code that brings up the interface (ifconfig scripts). All valid IPoIB partitions
(valid = have corresponding broadcast groups) should be initialized. By doing so we provide a centralized control
of the partitions and their IPoIB interfaces through the SM.

Please advice

Eitan

Hal Rosenstock wrote:
> Hi Roland,
> 
> I have a port which only has the full default partition configured but
> ifconfig allows an IPoIB interface with a PKey which is not in the Pkey
> table. Shouldn't the ifconfig fail for this (rather than the subsequent
> ping) ? 
> 
> -- Hal
> 
> smpquery pkeys 1 1
>    0: 0xffff 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
>    8: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
>   16: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
>   24: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
>   32: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
>   40: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
>   48: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
>   56: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
> 64 pkeys capacity for this port
> 
> echo 0x8001 > /sys/class/net/ib0/create_child
> 
> /sbin/ifconfig ib0.8001 192.168.2.1
> 
> ping -b 192.168.2.255
> WARNING: pinging broadcast address
> PING 192.168.2.255 (192.168.2.255) 56(84) bytes of data.
>