• TransportProtocols
• 11January2024

Attendees

• glebius@
• rscheff@
• rrs@
• tuexen@

Ongoing Short Term Projects

• glebius@ asks whether it makes sense to improve the TCP timer precision. tuexen@ states that this is very useful for testing purposes. glebius@ will provide a patch to tuexen@ for testing and tuexen@ will provide feedback, if such a patch us useful for FreeBSD in general. This applies to the default stack only, not the the RACK or BBR stack, which uses HPTS for timers. Setting the sysctl variable kern.timecounter.alloweddeviation to zero allows the timers to run of very precisely, which is useful when running packetdrill. However, it affects the overall system performance.

• At least for testing purposes (packetdrill) it would be good to have LRO support for tun interfaces. tuexen@ suggested to generalize LRO to not depend on an Ethernet header being present. gallatin@ prefers to not make the LRO code more complex, since it most likely will impact the performance. tuexen@ has implemented LRO support for the tap interfaces. packetdrill support will be committed soon.
• BBLog is missing a man page. tuexen@ will write one.
• tuexen@ will add tests for handling RST ACK segments in all states and test the base, RACK and BBR stack.

• rscheff@ wants feedback for D41715, which is based on a patch from VMWare for CUBIC. cc@ will tested and reviewed and rscheff@ will integrate the feedback. Also cc@ should look at D41672.

• Fatal trap NUM: page fault in in_pcbbind_setup: addressed in D42084. glebius@ will look at it.

• D42851 will be improved to remove socket option code. rscheff@ will do this and then wants feedback.

• rscheff@ wants feedback on D42906. tuexen@ is fine with it, rrs@ should look at it after the holidays.

• rscheff@ is using D42980 for testing.

• PR 275169 is based on the vland and the TCP layer using the same field for different purposes. Since this is a different times, it is OK. But it needs to be done in a correct way. glebius will provide a patch. He will also re-activate D35199 which would not mitigate the bug, but allow faster finding of it.

• rgrimes@ reports that FreeBSD using the default parameters can not saturate a Gigabit pipe with a delay used by recent access technologies. He will test some parameter changes and report back.
• glebius@ is still looking at cleaning up the handling of the UDP encapsulation port in the TCP stack. He wants feedback from rrs@. He brought up an idea the align the data at the end of an mbuf cluster instead of the beginning. This would give memory to be used for other things without the requirement of allocating it.
• glebius@ was trying to clean up the handling of the UDP encapsulation port of TCP. Moving it to a function argument is an intrusive change. He suggested to do it once an pass a pointer to a structure around. This way information can be added simply. glebius will work on it.
• It was discussed to make the handling of the RACK stack in the upcoming version 14.1 like the handling in FreeBSD CURRENT. glebius@ will work on this.
• rscheff@ brought up issues in the base stack and the RACK stack which can be improved by not throwing away the score board on the first RTO. He also presented some follow-up issues. rrs@ will look into improving the RACK stack to not throw away the score board on the first RTO.

Ongoing Longer Term Projects

• Now the RACK and the BBR stack are compiled by default in head. rrs@ will remove the BBR stack, since it has several limitations. tuexen@ will mark it as deprecated. We discussed if the RACK stack could be made the default and what should drive this decision. tuexen@ will reach out to the mailing list to ask people to test the RACK stack and provide feedback. In January, we will look again at the decision process based on the feedback we got. Feedback received:
  • You need to compile in the TCPHPTS. It is a module now, glebius@ will fix issues resulting a panic().
  • RACK is on the loopback interface slower than the base stack (CPU limited). olivier@ has a script to test combinations of stacks and CC modules.
  • A problem with RACK an pf, which couldn't be reproduced by olivier@.
• There seem to be some BBR users. Try to get them testing RACK.
• It was discussed that it would be a good idea to move the freebsd stack from ticks to micro seconds.

• rscheff@ is improving AccECN code: D36303. rrs@ will review it and implement it for the rack stack. Also the interaction between LRO and AccECN++ has to be taken into account. D42563 further adds the support of ACKofACK.

• D23230 is implementing ECN++. rrs@ will review it.

• tuexen@ wants to write a tool which dumps the BBLog information of a TCP endpoint from a life system or a core. Using kvm_read() has drawbacks as glebius@ pointed out, using a python kgdb script may be an alternative. An alternative is to write a python kgdb script which pumps data into tcplog_dumper. This would allow to minimize code duplication. glebius@ will try to work on this soon.

• The handling on ECN with TSO by NICs was discussed. It was decided to get gallatin@ involved.

Next Meeting

25 January 2024 @ 1500 UTC using FreeBSDTCPCall