Change Details

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).

NOTE: this diff requires D26449 as a pre-requisite. 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 ofNOTE: this diff requires D26449 as a pre-requisite. 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).