On 05/02/2015 15:48, Eric Dumazet wrote: > On Thu, 2015-02-05 at 14:44 +0100, Michal Kazior wrote: > >> I do get your point. But 1.5ms is really tough on Wi-Fi. >> >> Just look at this: >> >> ; ping 192.168.1.2 -c 3 >> PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. >> 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=1.83 ms >> 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=2.02 ms >> 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=1.98 ms > > Thats a different point. > > I dont care about rtt but TX completions. (usually much much lower than > rtt) On wired network perhaps, but definitely not on Wi-Fi. With aggregation, you may send up to 4ms of data before the receiver can acknowledge anything. But you have to gain access to the channel first, so you may wait while others finish off their 4ms transmissions. And this does not account for retransmissions. And aggregation is not the only problem as far as bufferbloat is concerned. I don't even want to think about powersave. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
