John Heffner wrote:
Rick Jones wrote:
Like I said the consumers of this are a triffle well, anxious :)
Just curious, did you or this customer try with F-RTO enabled? Or is
this case you're dealing with truly hopeless?
F-RTO was mentioned to the customer and I'm awaiting their response
David Miller wrote:
From: Rick Jones [EMAIL PROTECTED]
Date: Thu, 30 Aug 2007 18:07:13 -0700
Anyhow, I'll try grubbing around the source code (already doing that to
see about writing a pet tcp cong module) but if pointers to the likely
relevant files were available I could try to help
From: Rick Jones [EMAIL PROTECTED]
Date: Fri, 31 Aug 2007 11:11:37 -0700
At the risk of showing my ignorance (what me worry about that?-) I
presume this is then an interface expecting to take-in jiffies? That
means the user has to know the value of HZ which can be (IIRC) one of
three
I managed to find iproute2 sources (they were debian lenny/testing
2.6.20-1) and applied the patch, and figured-out how to add a host route
back to one of my systems. I then did a change to set rto_min to 300.
I started a tcpdump and then a netperf, and then forces some
retransmissions the
From: Rick Jones [EMAIL PROTECTED]
Date: Fri, 31 Aug 2007 13:59:50 -0700
ip is at tcp_rto_min+0x20/0x40
diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
index 1ee7212..bbad2cd 100644
--- a/net/ipv4/tcp_input.c
+++ b/net/ipv4/tcp_input.c
@@ -560,7 +560,7 @@ static u32 tcp_rto_min(struct
David Miller wrote:
From: Rick Jones [EMAIL PROTECTED]
Date: Fri, 31 Aug 2007 13:59:50 -0700
ip is at tcp_rto_min+0x20/0x40
diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
index 1ee7212..bbad2cd 100644
--- a/net/ipv4/tcp_input.c
+++ b/net/ipv4/tcp_input.c
@@ -560,7 +560,7 @@
From: Rick Jones [EMAIL PROTECTED]
Date: Fri, 31 Aug 2007 15:20:52 -0700
I'm going to go ahead and take a look at input vs output units and
differences between those with rto_min vs rtt.
You better because that's one of the last non-trivial emails you'll
get for me over the next few days
Enable configuration of the minimum TCP Retransmission Timeout via
a new sysctl tcp_rto_min to help those who's networks (eg cellular)
have quite variable RTTs avoid spurrious RTOs.
Signed-off-by: Rick Jones [EMAIL PROTECTED]
Signed-off-by: Lamont Jones [EMAIL PROTECTED]
---
diff -r 06d7322848a3
From: Rick Jones [EMAIL PROTECTED]
Date: Thu, 30 Aug 2007 17:09:04 -0700 (PDT)
Enable configuration of the minimum TCP Retransmission Timeout via
a new sysctl tcp_rto_min to help those who's networks (eg cellular)
have quite variable RTTs avoid spurrious RTOs.
Signed-off-by: Rick Jones
David Miller wrote:
From: Rick Jones [EMAIL PROTECTED]
Date: Thu, 30 Aug 2007 17:09:04 -0700 (PDT)
Enable configuration of the minimum TCP Retransmission Timeout via
a new sysctl tcp_rto_min to help those who's networks (eg cellular)
have quite variable RTTs avoid spurrious RTOs.
Rick Jones wrote:
Like I said the consumers of this are a triffle well,
anxious :)
Just curious, did you or this customer try with F-RTO enabled? Or is
this case you're dealing with truly hopeless?
-John
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a
From: Rick Jones [EMAIL PROTECTED]
Date: Thu, 30 Aug 2007 18:07:13 -0700
Anyhow, I'll try grubbing around the source code (already doing that to
see about writing a pet tcp cong module) but if pointers to the likely
relevant files were available I could try to help thrash-out the routing
12 matches
Mail list logo
