LGTM.
I think for those who want newly accepted connections to use a "new" default stack, there is a mechanism using tcpsso that could be used to (attempt to) change the listening socket's stack so that new connections use that stack. This would need to be run for all desired listening sockets though.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Nov 3 2025
Nov 3 2025
Nov 2 2025
Nov 2 2025
Oct 22 2025
Oct 22 2025
Oct 17 2025
Oct 17 2025
Oct 16 2025
Oct 16 2025
Oct 3 2025
Oct 3 2025
Sep 25 2025
Sep 25 2025
Aug 29 2025
Aug 29 2025
Aug 21 2025
Aug 21 2025
peter.lei_ieee.org added inline comments to D51985: vtnet.4: improve existing descriptions and add missing ones.
Aug 8 2025
Aug 8 2025
Jul 24 2025
Jul 24 2025
Jul 21 2025
Jul 21 2025
Jul 20 2025
Jul 20 2025
Jul 19 2025
Jul 19 2025
Jul 7 2025
Jul 7 2025
Jun 27 2025
Jun 27 2025
Jun 26 2025
Jun 26 2025
Jun 17 2025
Jun 17 2025
Jun 11 2025
Jun 11 2025
May 1 2025
May 1 2025
Apr 4 2025
Apr 4 2025
Apr 3 2025
Apr 3 2025
Mar 31 2025
Mar 31 2025
Mar 20 2025
Mar 20 2025
Feb 6 2025
Feb 6 2025
Jan 9 2025
Jan 9 2025
Jan 8 2025
Jan 8 2025
Nov 14 2024
Nov 14 2024
Nov 13 2024
Nov 13 2024
Nov 2 2024
Nov 2 2024
Sep 5 2024
Sep 5 2024
Aug 9 2024
Aug 9 2024
Aug 7 2024
Aug 7 2024
Jul 27 2024
Jul 27 2024
peter.lei_ieee.org accepted D46141: tcp: retire sysctl variable functions_inherit_listen_socket_stack.
Jul 26 2024
Jul 26 2024
peter.lei_ieee.org added a comment to D46140: tcp: make sysctl variables ack_war_timewindow and ack_war_cnt vnet specific.
We need these applied to rack_bbr_common.c as well.
Jul 24 2024
Jul 24 2024
Jul 23 2024
Jul 23 2024
Jul 21 2024
Jul 21 2024
I don't have a strong opinion on the default flag state (DEFAULT_OK or DEFAULT_NOT_OK), so this seems fine to me.
Jul 20 2024
Jul 20 2024
Jun 27 2024
Jun 27 2024
Jun 4 2024
Jun 4 2024
May 30 2024
May 30 2024