On Tue, 2015-01-06 at 18:17 +0000, Erik Grinaker wrote: > Yes, pcap was taken on receiver (195.159.221.106). > > > If the sender is broken, changing the kernel on receiver wont help. > > > > BTW not using sack (on 54.231.132.98) is terrible for performance in > > lossy environments. > > It may well be that the sender is broken; however, the sender is > Amazon S3, so I do not have any control over it. And in any case, the > problem goes away with 3.11.10 on receiver, but persists with 3.12.0 > (or later) on receiver, so there must be some change in 3.12.0 which > has caused this to trigger.
In fact I saw nothing obviously wrong in pcap (but I have not done a full analysis) It might simply be an application bug, triggering a timeout too soon. A kernel change can be good, but by changing timings a bit, trigger application bugs. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
