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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 1 Nov 2016 08:15:15 +0000 From: Ilya Lesokhin <ilyal@...lanox.com> To: "netdev@...r.kernel.org" <netdev@...r.kernel.org> CC: Eric Dumazet <eric.dumazet@...il.com>, tls-fpga-sw-dev <tls-fpga-sw-dev@...lanox.com> Subject: Why does tcp collapse behavior depend on nr_frags? Hi, I've notice that tcp_can_collapse() returns false if skb_shinfo(skb)->nr_frags != 0. Is there a reason why we want to base the collapse decision in retransmission on whether the data is located in a frag or the linear part? The relevant commit is tcp: collapse more than two on retransmission ('4a17fc3add594fcc1c778e93a95b6ecf47f630e5') Thanks, Ilya
Powered by blists - more mailing lists