Page MenuHomeFreeBSD

tcp/lro: If timestamps mismatch or it's a FIN, force flush.
ClosedPublic

Authored by sepherosa_gmail.com on Aug 4 2016, 8:50 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mar 2 2024, 5:31 AM
Unknown Object (File)
Mar 2 2024, 5:30 AM
Unknown Object (File)
Feb 12 2024, 8:44 AM
Unknown Object (File)
Dec 30 2023, 11:11 PM
Unknown Object (File)
Dec 23 2023, 8:42 AM
Unknown Object (File)
Dec 23 2023, 7:26 AM
Unknown Object (File)
Dec 22 2023, 6:49 PM
Unknown Object (File)
Dec 22 2023, 6:49 PM
Subscribers

Details

Summary
This keeps the segments/ACK/FIN delivery order.

Before this patch, it was observed: if A sent FIN immediately after
an ACK, B would deliver FIN first to the TCP stack, then the ACK.
This out-of-order delivery causes one unnecessary ACK sent from B.

Obtained from:  gallatin, rrs

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

sepherosa_gmail.com retitled this revision from to tcp/lro: If timestamps mismatch or it's a FIN, force flush..
sepherosa_gmail.com updated this object.
sepherosa_gmail.com edited the test plan for this revision. (Show Details)
sys/netinet/tcp_lro.c
852

Should there be added:

if (force_flush)

return (TCP_LRO_CANNOT);

If no match is found in the list?

sys/netinet/tcp_lro.c
852

Ah, yeah, it was in the original patch from rrs, got lost by me :P

Don't create entry for segments cant be further aggregated/delayed. Noticed-by: hps

hselasky edited edge metadata.

Looks good to me.

--HPS

gallatin edited edge metadata.
This revision was automatically updated to reflect the committed changes.