Hello, You can also consider the idea of having 3 coordinates for start svc: idx_svc_tab (0 or 1), idx_svc_row (0..IP_VS_SVC_TAB_SIZE-1) and idx_svc for index in row's chain. On new packet this will
Hi, My (maybe not so great) idea was to avoid repeating the svc on each packet. It's possible for a packet to start with a destination and user space must consider then as belonging to the last svc r
Hello, At this point idx_svc is incremented and we stop at the middle of dest list, so we need ctx->idx_svc-- too. And now what happens if all dests can not fit in a packet? We should start next pack
A common operation for userspace applications managing ipvs is to dump all services and all destinations and then sort out what needs to be done. Previously this could only be accomplished by issuing