On Mon, Dec 17, 2018 at 10:02:19AM -0600, Eric Blake wrote: > On 12/17/18 2:10 AM, Yuval Shaia wrote: > > The control over the RDMA device's GID table is done by updating the > > device's Ethernet function addresses. > > Usually the first GID entry is determined by the MAC address, the second > > by the first IPv6 address and the third by the IPv4 address. Other > > entries can be added by adding more IP addresses. The opposite is the > > same, i.e. whenever an address is removed, the corresponding GID entry > > is removed. > > > > The process is done by the network and RDMA stacks. Whenever an address > > is added the ib_core driver is notified and calls the device driver > > add_gid function which in turn update the device. > > > > To support this in pvrdma device we need to hook into the create_bind > > and destroy_bind HW commands triggered by pvrdma driver in guest. > > Whenever changed is made to the pvrdma port's GID table a special QMP > > s/changed/a change/ > > > messages is sent to be processed by libvirt to update the address of the > > s/messages/message/
Thanks! Will fix and send v8 > > > backend Ethernet device. > > > > Signed-off-by: Yuval Shaia <yuval.sh...@oracle.com> > > Reviewed-by: Marcel Apfelbaum<marcel.apfelb...@gmail.com> > > --- > > > -- > Eric Blake, Principal Software Engineer > Red Hat, Inc. +1-919-301-3266 > Virtualization: qemu.org | libvirt.org
