On Wed, 2010-03-10 at 14:55 -0800, Stephen Hemminger wrote: > TCP does slow start so it won't fill up window unless ack's come back. > http://en.wikipedia.org/wiki/Slow-start > > If you have a bad TCP (like MacOS) or some crazy middlebox that delays > the acknowledgments, then the window will increase much slower because > the extended delay of the ack's would slow growth. > > The other possibility is that the receive window on the other side > is too small. Both endpoints have to cooperate to allow for large > amounts of in-flight data. Yes, I was thinking of the slow-start possibility too. But then the sending window would still have to grow over time with more acks received, but it does not (see packets 100 to 350 or so). The receive window looks like being a lot larger than what is transmitted after the ack is received (at least I can see ca. 64k advertised in that section). Maybe I just read the dump wrong, but I still can't make sense of it (and fix my problem). Do have an idea what I could change? Cheers, Andres -- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
