Re: [dpdk-dev] [PATCH] drivers/net/bonding: fix bug for lacp negotiation failed

2020-07-10 Thread Wei Hu (Xavier)
Hi, Thomas Monjalon The patch V2 has been sent by luyicai, and V2 is good to me. Thanks, Xavier On 2020/7/11 5:07, Thomas Monjalon wrote: Still no review. Please give your real name in the Signed-off so it can be merged. 24/06/2020 12:43, Thomas Monjalon: Any review please? 19/05/202

Re: [dpdk-dev] [PATCH] drivers/net/bonding: fix bug for lacp negotiation failed

2020-07-10 Thread Thomas Monjalon
Still no review. Please give your real name in the Signed-off so it can be merged. 24/06/2020 12:43, Thomas Monjalon: > Any review please? > > 19/05/2020 13:18, luyicai: > > When two host is connected directly without any devices like switch, > > and also enable dedicated tx/rx queues on bonding

Re: [dpdk-dev] [PATCH] drivers/net/bonding: fix bug for lacp negotiation failed

2020-06-24 Thread Thomas Monjalon
Any review please? 19/05/2020 13:18, luyicai: > When two host is connected directly without any devices like switch, > and also enable dedicated tx/rx queues on bonding devices slaves, > rx_machine_update would recieving partner lacp negotiation packets, > which partner's port mac filled with zero

[dpdk-dev] [PATCH] drivers/net/bonding: fix bug for lacp negotiation failed

2020-05-19 Thread luyicai
When two host is connected directly without any devices like switch, and also enable dedicated tx/rx queues on bonding devices slaves, rx_machine_update would recieving partner lacp negotiation packets, which partner's port mac filled with zeros. So in this situation, it would never go rx_machine b

[dpdk-dev] [PATCH] drivers/net/bonding: fix bug for lacp negotiation failed

2020-05-19 Thread luyicai
When two host is connected directly without any devices like switch, and also enable dedicated tx/rx queues on bonding devices slaves, rx_machine_update would recieving partner lacp negotiation packets, which partner's port mac filled with zeros. So in this situation, it would never go rx_machine b