Hi, all I use dpdk LACP bond for long time large flow test, there are LACP broken chain. The dpdk log is as follow: Bond 1: slave id 0 distributing stopped. Bond 1: slave id 1 distributing stopped.
Through the analysis of code , LACP protocol packets are handled by eal-intr-thread thread, at the same time, the thread will also deal with the other driver interrupt event and query the NIC card state . And each polling thread is waiting for a long time that is leading to the switch disconnection timeout. On the generic x86 OS server, has it been considered that the eal-intr-thread thread can 't get a timely scheduling, and that would result in LACP timeout and Link broken chain? Or has it been considered that LACP bond would be put on a single thread, not shared with others?
