Re: bizarre network timing problem

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Felix von Leitner
Date: Thursday, October 18, 2007 - 2:42 am

> the packet trace was a bit too cooked perhaps, but there were indications 

Does TCP use different window sizes on loopback?  Why is this not
happening on ethernet?

How could I test this theory?

My initial idea was that it has something todo with the different MTU on
loopback.  My initial block size was 16k, but the problem stayed when I
changed it to 64k.

Felix
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: bizarre network timing problem, Chuck Ebbert, (Wed Oct 17, 2:17 pm)
Re: bizarre network timing problem, Felix von Leitner, (Wed Oct 17, 3:00 pm)
Re: bizarre network timing problem, Rick Jones, (Wed Oct 17, 3:16 pm)
Re: bizarre network timing problem, Felix von Leitner, (Thu Oct 18, 2:42 am)
Re: bizarre network timing problem, Rick Jones, (Thu Oct 18, 10:22 am)
Re: bizarre network timing problem, Felix von Leitner, (Fri Nov 2, 3:11 pm)
Re: bizarre network timing problem, Rick Jones, (Fri Nov 2, 3:33 pm)
Re: bizarre network timing problem, Felix von Leitner, (Fri Nov 2, 3:38 pm)
Re: bizarre network timing problem, Rick Jones, (Fri Nov 2, 3:58 pm)
Re: bizarre network timing problem, Felix von Leitner, (Fri Nov 2, 4:23 pm)
Re: bizarre network timing problem, Rick Jones, (Tue Nov 6, 2:12 pm)