netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Why does tcp collapse behavior depend on nr_frags?
@ 2016-11-01  8:15 Ilya Lesokhin
  2016-11-01 13:33 ` Eric Dumazet
  0 siblings, 1 reply; 8+ messages in thread
From: Ilya Lesokhin @ 2016-11-01  8:15 UTC (permalink / raw)
  To: netdev@vger.kernel.org; +Cc: Eric Dumazet, tls-fpga-sw-dev

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

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2016-11-01 19:35 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-11-01  8:15 Why does tcp collapse behavior depend on nr_frags? Ilya Lesokhin
2016-11-01 13:33 ` Eric Dumazet
2016-11-01 15:32   ` [PATCH net-next] tcp: enhance tcp collapsing Eric Dumazet
2016-11-01 16:35     ` Neal Cardwell
2016-11-01 17:39       ` Eric Dumazet
2016-11-01 17:47         ` Eric Dumazet
2016-11-01 17:53     ` [PATCH v2 " Eric Dumazet
2016-11-01 19:35       ` Neal Cardwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).