Re: [libvirt] [PATCH RESEND] qemu: Process RDMA GID state change event

2018-11-06 Thread Michal Privoznik
On 11/05/2018 08:27 PM, Yuval Shaia wrote: > On Mon, Nov 05, 2018 at 05:42:10PM +0100, Michal Privoznik wrote: >> [There is no need to resend your patch just to put yourself onto CC >> list. The review policy is always "reply to all"] > > Hi Michal, > > Actually i posted the "RESEND" as my

Re: [libvirt] [PATCH RESEND] qemu: Process RDMA GID state change event

2018-11-05 Thread Yuval Shaia
On Mon, Nov 05, 2018 at 05:42:10PM +0100, Michal Privoznik wrote: > [There is no need to resend your patch just to put yourself onto CC > list. The review policy is always "reply to all"] Hi Michal, Actually i posted the "RESEND" as my original mail was not shown up in

Re: [libvirt] [PATCH RESEND] qemu: Process RDMA GID state change event

2018-11-05 Thread Michal Privoznik
[There is no need to resend your patch just to put yourself onto CC list. The review policy is always "reply to all"] On 11/05/2018 11:50 AM, Yuval Shaia wrote: > This event is emitted on the monitor when a GID table in pvrdma device > is modified and the change needs to be propagate to the

[libvirt] [PATCH RESEND] qemu: Process RDMA GID state change event

2018-11-05 Thread Yuval Shaia
This event is emitted on the monitor when a GID table in pvrdma device is modified and the change needs to be propagate to the backend RDMA device's GID table. 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