Change Details

Continuation of D26449. Current code on mbuf flowid for both transit and outbound traffic. For locally-originated connections we currently don't calculate inp_flowid. With multipath enabled, it is necessary to enable load balancing. As a performance optimisation, start calculating these hashes after inserting first multipath route in vnet (V_hash_outbound).

Continuation of D26449. Current code relies on mbuf flowid for both transit and outbound traffic. By default, flowid is filled in with `inp_flowid` for pcb-based outgoing connections. However, `inp_flowid` is not currently calculated. This calculation is necessary to enable load balancing. As this may introduce performance penalcy, start calculating these hashes after inserting first multipath route in vnet (V_hash_outbound).

Continuation of D26449. Current code relies on mbuf flowid for both transit and outbound traffic. For locally-originated connections we currently don't calculate inp_flowiBy default, flowid is filled in with `inp_flowid` for pcb-based outgoing connections. However, `inp_flowid` is not currently calculated. With multipath enabled, itThis calculation is necessary to enable load balancing. As aAs this may introduce performance optimisationpenalcy, start calculating these hashes after inserting first multipath route in vnet (V_hash_outbound).