| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1307875698.2872.130.camel@edumazet-laptop> Date: Sun, 12 Jun 2011 12:48:18 +0200 From: Eric Dumazet <eric.dumazet@...il.com> To: Joris van Rantwijk <joris@...isvr.nl> Cc: netdev@...r.kernel.org Subject: Re: Question about LRO/GRO and TCP acknowledgements Le dimanche 12 juin 2011 à 11:30 +0200, Joris van Rantwijk a écrit : > On 2011-06-12, Eric Dumazet <eric.dumazet@...il.com> wrote: > > > As far as I can see, current code will send just one ACK per > > > coalesced GRO bundle, while the sender expects one ACK per two > > > segments. > > > One ACK carries an implicit ack for _all_ previous segments. If sender > > only 'counts' ACKs, it is a bit dumb... > > It may be dumb, but it's what the RFCs recommend and it's what Linux > implements. > > RFC 5681: > "During slow start, a TCP increments cwnd by at most SMSS bytes for > each ACK received that cumulatively acknowledges new data." > Note also RFC says: The RECOMMENDED way to increase cwnd during congestion avoidance is to count the number of bytes that have been acknowledged by ACKs for new data. So your concern is more a Sender side implementation missing this recommendation, not GRO per se... GRO kicks when receiver receives a train of consecutive frames in his NAPI run. In order to really reduce number of ACKS, you need to receive 3 frames in a very short time. This leads to the RTT rule : "Note that during congestion avoidance, cwnd MUST NOT be increased by more than SMSS bytes per RTT" So GRO, lowering number of ACKS, can help sender to not waste its time on extra ACKS. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists