lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 6 Dec 2020 08:54:22 +0200 From: Eli Cohen <elic@...dia.com> To: Jason Wang <jasowang@...hat.com> CC: "Michael S. Tsirkin" <mst@...hat.com>, Cindy Lu <lulu@...hat.com>, <virtualization@...ts.linux-foundation.org>, <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] vdpa/mlx5: Use random MAC for the vdpa net instance On Fri, Dec 04, 2020 at 10:53:28AM +0800, Jason Wang wrote: > > On 2020/12/3 下午8:24, Eli Cohen wrote: > > > > It is mentioned in Parav's patchset that this will be coming in a > > > > subsequent patch to his vdpa tool. > > > So I think kernel has two options: > > > - require a mac when device is created, we supply it to guest > > Yes, the driver should always set VIRTIO_NET_F_MAC and provide a MAC - > > either random or whatever configured using the vdpa too. > > > A questions here, I think current mlx5 vdpa works for VF only. So I think > the VF should have a given MAC? If yes, can we use that MAC? > The MAC assigned to VF is by the NIC implementation. Both ther regular NIC driver and the VDPA implementation can co-exist so we can't use the NIC's MAC for VDPA. We want to steer traffic based on its destination MAC address to either VDPA or regular NIC.
Powered by blists - more mailing lists