>> however, after fixing things so the initial cwind isn't hosed, i get a >> little better story: > > so, actually, i think this is the root cause. the intial cwind is misset for > loopback. > i but that the symptom folks will see is that /net/tcp/stats shows > fragmentation when > performance sucks. evidently there is a backoff bug in sources' tcp, too.
What is your cwind change? -- David du Colombier
