> Actually, our TCP stacks should ack immediately when any out of order
> data exists in the receive queue. This was broken in 2.1.x until
> 2.1.127, it is still broken in 2.0.36prexxx because Alan didn't want
> to put that change in at this point.
Even when SACK is enabled on that connection?
-cw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/