Hi,

I'm interested in the Linux kernel's support for per-flow IPv4 ECMP (i.e. 
consistent path selection based on a hash of the connection tuple).  I'd been 
led to believe[1] that this depended on the route cache, which was removed in 
3.6.

However, I tested a route with multiple next hops on a 3.10 and 3.13 kernel, 
and ECMP was per-flow!  Obviously I'm pleased that this was the case, but I'd 
like to understand why this is supported, and whether I can rely on it in 
future.

Could anyone give me a little clarification on whether this is now supported by 
some means other than the route cache, and whether that support is intended to 
be continued?

Thanks,
Matt

[1]: http://bird.network.cz/pipermail/bird-users/2014-February/008873.html
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to