From: Ben Greear <[EMAIL PROTECTED]> Date: Wed, 11 Apr 2007 11:50:18 -0700
> So, I would like to dig into this problem myself since no one else > is reporting this type of problem, but I am quite ignorant of the TCP > stack implementation. Based on the dup-acks I see on the wire, I assume > the TCP state machine is messed up somehow. Could anyone point me to > likely places in the TCP stack to start looking for this bug? Dup acks mean that packets are being dropped and there are thus holes in the sequence seen at the receiver. Likely what happens is that we hit the global memory pressure limit, start dropping packets, and never recover even after the memory pressure is within it's limits again. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
