David S. Miller wrote:
This was brought up before. It's the case where the system is acting
as a router, you have to consider that case and not just the one where
the local system is where the connections are originating from.
Your trick only works because of how routes are cached per-socket.
David S. Miller wrote:
So essentially you want per-flow multipathing. Except that you're
implementation
is over-optimizing it to the point where it's only per-flow for your specific
case where the connections are short lived and high rate.
This hurts long lasting connections.
So I'm pretty much
David S. Miller wrote:
Can you describe more precisely "the scenerios, that are relevant
to us"?
The scenarios we have in mind are setups in which a set of collaborating
servers steadly establish connections among each other with a very high rate.
This high rate requirement drove us to consider
David S. Miller wrote:
Can you describe more precisely the scenerios, that are relevant
to us?
The scenarios we have in mind are setups in which a set of collaborating
servers steadly establish connections among each other with a very high rate.
This high rate requirement drove us to consider
David S. Miller wrote:
So essentially you want per-flow multipathing. Except that you're
implementation
is over-optimizing it to the point where it's only per-flow for your specific
case where the connections are short lived and high rate.
This hurts long lasting connections.
So I'm pretty much
David S. Miller wrote:
This was brought up before. It's the case where the system is acting
as a router, you have to consider that case and not just the one where
the local system is where the connections are originating from.
Your trick only works because of how routes are cached per-socket.
6 matches
Mail list logo
