Richard Laing alliedtelesis.co.nz> writes:
> >>> Fair enough, I will look at making it a sysctl option. I guess the
> >>> default can be the current behaviour.
> Cheers
> Richard
>
Hi Richard,
Could you please share if this new patch for per-flow IPv4 ECMP has landed?
If so, which version
On Tue, Jul 28, 2015 at 11:11 PM, Michal Kubecek mkube...@suse.cz wrote:
On Tue, Jul 28, 2015 at 09:20:02PM +, Richard Laing wrote:
diff --git a/include/net/flow.h b/include/net/flow.h
index 8109a15..d1d933d 100644
--- a/include/net/flow.h
+++ b/include/net/flow.h
@@ -79,6 +79,10 @@
On 07/30/2015 04:12 AM, Tom Herbert wrote:
On Tue, Jul 28, 2015 at 11:11 PM, Michal Kubecek mkube...@suse.cz wrote:
On Tue, Jul 28, 2015 at 09:20:02PM +, Richard Laing wrote:
diff --git a/include/net/flow.h b/include/net/flow.h
index 8109a15..d1d933d 100644
--- a/include/net/flow.h
+++
From: Michal Kubecek mkube...@suse.cz
Date: Wed, 29 Jul 2015 08:11:48 +0200
Having both sysctl and per-route attribute would be perfect, of
course.
+1
--
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
Hello,
On Tue, 28 Jul 2015, Richard Laing wrote:
From: Richard Laing richard.la...@alliedtelesis.co.nz
Enable flow-based ECMP.
Currently if equal-cost multipath is enabled the kernel chooses between
equal cost paths for each matching packet, essentially packets are
On Tue, Jul 28, 2015 at 09:20:02PM +, Richard Laing wrote:
diff --git a/include/net/flow.h b/include/net/flow.h
index 8109a15..d1d933d 100644
--- a/include/net/flow.h
+++ b/include/net/flow.h
@@ -79,6 +79,10 @@ struct flowi4 {
#define fl4_ipsec_spiuli.spi
#define
On Tue, Jul 28, 2015 at 02:27:57AM +, Richard Laing wrote:
From: Richard Laing richard.la...@alliedtelesis.co.nz
Enable flow-based ECMP.
Currently if equal-cost multipath is enabled the kernel chooses between
equal cost paths for each matching packet, essentially packets are
On Tue, 28 Jul 2015 02:27:57 +
Richard Laing richard.la...@alliedtelesis.co.nz wrote:
From: Richard Laing richard.la...@alliedtelesis.co.nz
Enable flow-based ECMP.
Currently if equal-cost multipath is enabled the kernel chooses between
equal cost paths for each matching packet,
On Mon, Jul 27, 2015 at 7:27 PM, Richard Laing
richard.la...@alliedtelesis.co.nz wrote:
From: Richard Laing richard.la...@alliedtelesis.co.nz
Enable flow-based ECMP.
Currently if equal-cost multipath is enabled the kernel chooses between
equal cost paths for each matching packet, essentially
On Tue, Jul 28, 2015 at 2:02 PM, Tom Herbert t...@herbertland.com wrote:
On Mon, Jul 27, 2015 at 7:27 PM, Richard Laing
richard.la...@alliedtelesis.co.nz wrote:
From: Richard Laing richard.la...@alliedtelesis.co.nz
Enable flow-based ECMP.
Currently if equal-cost multipath is enabled the
On 07/29/2015 07:51 AM, Stephen Hemminger wrote:
On Tue, 28 Jul 2015 02:27:57 +
Richard Laing richard.la...@alliedtelesis.co.nz wrote:
From: Richard Laing richard.la...@alliedtelesis.co.nz
Enable flow-based ECMP.
Currently if equal-cost multipath is enabled the kernel chooses between
On 07/29/2015 09:02 AM, Tom Herbert wrote:
On Mon, Jul 27, 2015 at 7:27 PM, Richard Laing
richard.la...@alliedtelesis.co.nz wrote:
From: Richard Laing richard.la...@alliedtelesis.co.nz
Enable flow-based ECMP.
Currently if equal-cost multipath is enabled the kernel chooses between
equal
On 07/29/2015 09:15 AM, Tom Herbert wrote:
On Tue, Jul 28, 2015 at 2:02 PM, Tom Herbert t...@herbertland.com wrote:
On Mon, Jul 27, 2015 at 7:27 PM, Richard Laing
richard.la...@alliedtelesis.co.nz wrote:
From: Richard Laing richard.la...@alliedtelesis.co.nz
Enable flow-based ECMP.
From: Richard Laing richard.la...@alliedtelesis.co.nz
Enable flow-based ECMP.
Currently if equal-cost multipath is enabled the kernel chooses between
equal cost paths for each matching packet, essentially packets are
round-robined between the routes. This means that packets from a single
flow
14 matches
Mail list logo