Date: Mon, 12 Feb 2024 13:34:42 +0000 From: Benoit Chesneau <benoitc@enki-multimedia.eu> To: Konstantin Belousov <kostikbel@gmail.com> Cc: "freebsd-net@FreeBSD.org" <freebsd-net@freebsd.org> Subject: Re: mlx5en issue with SR-IOV when using in the bridge Message-ID: <SqpypwZsSMYMn3QVZ49JabJZLw7yb3f3Jfsp9ySF24que6KsgBAFEhnKAl-0Ek_LF0GvJrDSV8K9rewNbnSvP6jqVGLIzXELMyHDEZpvSkI=@enki-multimedia.eu> In-Reply-To: <Zcnq2Jgx-EsIEqao@kib.kiev.ua> References: <7L4ctsvv8st_6uOSAw8Li1SvAPsNYXPWjv3rRepGpwcRdl900YajxFSLe3frQl4hUE28PKU5lf98gRpN7WlZG7u2FWgOf3BImZu4spzI3Sg=@enki-multimedia.eu> <ZchEDCj66kNE_nKD@kib.kiev.ua> <VHVL58KsFi0lfUvo1Jz8Vfd2TuGQfzAEDOH8Zh-hDLIbqIpJv45Fh0wuKVaIVOtkC36WZq_QRWqTbUy4NszEgg871l07fG08N7BXRSqV1RI=@enki-multimedia.eu> <Zcnq2Jgx-EsIEqao@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
OK . I guesss it's about porting some parts from the linux driver, but the = code is slightly different today.. Is there any card that support correctly SR-IOV ? chelsio (but i don't know= where to source them) ? Intel ? Beno=C3=AEt On Monday, February 12th, 2024 at 10:54, Konstantin Belousov <kostikbel@gma= il.com> wrote: > On Mon, Feb 12, 2024 at 08:30:37AM +0000, Benoit Chesneau wrote: > > > Hi Konstantin, > > > > indeed the port is plugged to a switch. The port is enabled. So yes tha= t probably is. Is this a firmware issue or can it be solved in the driver? > > It is driver issue, and requires some (significant) driver updates. > > > Beno=C3=AEt > > > > On Sunday, February 11th, 2024 at 04:50, Konstantin Belousov kostikbel@= gmail.com wrote: > > > > > On Sat, Feb 10, 2024 at 09:23:36AM +0000, Benoit Chesneau wrote: > > > > > > > I have tested the following scenario: > > > > > > > > Setup the mellanox driver with SRIOV: > > > > > > > > ``` > > > > $ sudo more /etc/iov/mce0.conf > > > > PF { > > > > device: "mlx5_core0"; > > > > num_vfs: 8; > > > > } > > > > > > > > DEFAULT { > > > > passthrough: true; > > > > } > > > > > > > > VF-0 { > > > > mac-addr: "02:01:02:02:01:00"; > > > > } > > > > > > > > VF-1 { > > > > mac-addr: "02:01:02:02:01:01"; > > > > } > > > > > > > > VF-2 { > > > > passthrough: false;} > > > > > > > > ``` > > > > > > > > With one VF in the vm answering to a specific vlan, and one jail on= the host using vnet with the PF in a bridge and a epair interface added to= this bridge. > > > > > > > > When I am pinging from the jail to the VF in the vm , the vm receiv= e the ping or arp requests. But the jail doesn't receive the response. In a= same manner , when I ping from the VM to the jail, the host is not found. = bridge arp doesn't return the vm mac address. > > > > > > > > All the hosts has the PF interface set in promiscuous mode but this= doesn't seem to be enough to allows the bridge to learn other mac ids. Whe= n I directly add the IP to PF, Ping works from the vm to the PF, the revers= e is also true. > > > > > > > > Do I miss a setting? Is this expected with mellanox cards? What sho= udl I look for? > > > > > > Do you have the port plugged into a switch and the port enabled? > > > I suspect VFs do not have enough hairpin code to do proper loopback > > > communications, and I certain that multicast loopback does not work.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?SqpypwZsSMYMn3QVZ49JabJZLw7yb3f3Jfsp9ySF24que6KsgBAFEhnKAl-0Ek_LF0GvJrDSV8K9rewNbnSvP6jqVGLIzXELMyHDEZpvSkI=>