Subject: Re: [PATCH v4 for-next 04/12] IB/ipoib: Return IPoIB devices matching connection parameters

From: Haggai Eran <haggaie-VPRAkNaXOzVWk0Htik3J/[email-masked]>
Date: Thu, 21 May 2015 09:33:46 +0300

On 21/05/2015 08:48, Or Gerlitz wrote:
> On Thu, May 21, 2015 at 8:33 AM, Haggai Eran <haggaie-VPRAkNaXOzVWk0Htik3J/[email-masked]> wrote:
>> On 20/05/2015 02:55, Jason Gunthorpe wrote:
>>> On Sun, May 17, 2015 at 08:51:00AM +0300, Haggai Eran wrote:
>>>>> From: Guy Shapiro <guysh-VPRAkNaXOzVWk0Htik3J/[email-masked]>
>>>>>
>>>>> Implement the get_net_device_by_port_pkey_ip callback that returns network
>>>>> device to ib_core according to connection parameters. Check the ipoib
>>>>> device and iterate over all child devices to look for a match.
>>> Can you give a run down on how to actually set this up? Like what
>>> shell command do you execute?
>>
>> Sure.
>>
>> There are two methods to create new child interface for IPoIB.
>> For a specific P_Key, write the desired P_Key to the create_child sysfs
>> file:
>> # echo 0x8000 > /sys/class/net/ib0/create_child
>> This creates a new interface ib0.8000 operating with P_Key 0x8000.
> 
> 0x8000 is practically zero (bits 15-0), right? not sure this is a valid pkey.
Right, bad example :)

> 
> 
>> To create a new child interface on the default P_Key, its possible to
>> use iproute:
>> # ip link add link ib0 name ib0.1 type ipoib
> 
> you can use non default pkeys as well here.
> 
> $ ip link add link ib0 name ib0.1 type ipoib pkey 0x8001
> 

Right. I think when we started development of the namespaces patches
these child interfaces (rtnetlink with pkey) didn't work for us, but I
checked now on an updated kernel and they do.

Haggai
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email-masked]
More majordomo info at  http://vger.kernel.org/majordomo-info.html