Re: How do I generate and set a GUID on an Ethernet VF with ConnectX-4?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On May 31, 2017, at 6:16 PM, Robert LeBlanc <robert@xxxxxxxxxxxxx> wrote:
> 
> I think there may be more than just changing the MAC. The Mellanox
> documentation talks about unbinding and re-binding the VF.
Correct.. I thought you've already done that.
So basically the flow is as follow:
1. Create VFs on the hypervisor
2. Configure MAC addresses to the VFs on the Hypervisor
3. Unbind the VFs drivers
4. Bind back

This way, the VFs will reload with the configured data..
> The odd
> thing is that the MAC for the VF under the parent adapter is '0', but
> the othadapter itself has a MAC address. You had a good idea, but I think
> we are still missing something. I do think that changing the MAC is
> the right thing to get the GUID changed according to the Mellanox
> documentation.
> 
> 4: rs81p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state
> UP mode DEFAULT group default qlen 1000
>   link/ether 24:8a:07:1e:7c:60 brd ff:ff:ff:ff:ff:ff
>   vf 0 MAC 12:34:56:78:9a:bc, spoof checking off, link-state auto
>   vf 1 MAC 00:00:00:00:00:00, spoof checking off, link-state auto
> 8: rs81p1v1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
> DEFAULT group default qlen 1000
>   link/ether e6:17:5f:85:45:e6 brd ff:ff:ff:ff:ff:ff
> 17: rs81p1v0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
> state UP mode DEFAULT group default qlen 1000
>   link/ether ee:af:9f:66:2b:0c brd ff:ff:ff:ff:ff:ff
> # ibv_devices
>   device                 node GUID
>   ------              ----------------
>   mlx5_0              248a0703001e7c60
>   mlx5_2              0000000000000000
>   mlx5_4              0000000000000000
> ----------------
> Robert LeBlanc
> PGP Fingerprint 79A2 9CA4 6CC4 45DD A904  C70E E654 3BB2 FA62 B9F1
> 
> 
>> On Wed, May 31, 2017 at 2:28 AM, Majd Dibbiny <majd@xxxxxxxxxxxx> wrote:
>> 
>>> On May 30, 2017, at 8:55 PM, Robert LeBlanc <robert@xxxxxxxxxxxxx> wrote:
>>> 
>>> One problem we found with rping is that when the GUID is '0', it
>>> fails. However, all of the VFs that are created are created with a '0'
>>> GUID. How do I generate a GUID that will not conflict for the VFs?
>> Hi Robert,
>> 
>> IIRC, once you set a MAC address for a VF, the node guid will be derived automatically for it. Also, it can be controlled using iptool.
>> 
>> 
>>> Once I have a generated GUID, how do I set it on a VF using the inbox
>>> drivers? I can't find a /sys entry that will allow me to write it and
>>> the one mentioned in the Mellanox OFED doesn't exist.
>>> 
>>> I'll need to find a way to script this as part of my udev rules that
>>> adds the VFs.
>>> 
>>> Thank you,
>>> ----------------
>>> Robert LeBlanc
>>> PGP Fingerprint 79A2 9CA4 6CC4 45DD A904  C70E E654 3BB2 FA62 B9F1
>>> --
>>> 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
--
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




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux