Messages in this thread | | | Date | Wed, 4 Jun 2003 10:24:14 +1000 (EST) | From | James Morris <> | Subject | Re: fix TCP roundtrip time update code |
| |
On Tue, 3 Jun 2003, David Mosberger wrote:
> Martin> I tested this patch and it looks like it has cured my > Martin> mysterious TCP stalls. > > Yes, this sounds reasonable. I wasn't very clear on this point, but > "by going south" I meant that TCP is starting to misbehave. In > particular, you'll likely end up with the kernel aborting ESTABLISHED > TCP connections with extreme prejudice (and in violation of the TCP > protocol), because it thought that it had been unable to communicate > with the remote end for a _very_ long time. The net effect typically > is that you end up with one end having a connection that's in the > ESTABLISHED state and the other end having no trace of that > connection.
David,
This might be the solution to one of the 'must-fix' bugs for the networking, which nobody so far was quite able to track down.
- James -- James Morris <jmorris@intercode.com.au>
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |