Skip to content

add documentation for the advanced configuration option 'enable_lwip_tcp_sack' #5234

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: next
Choose a base branch
from

Conversation

RubenKelevra
Copy link
Contributor

Description:

add documentation for the advanced configuration option 'enable_lwip_tcp_sack'

Related issue (if applicable): fixes

Pull request in esphome with YAML changes (if applicable):

Checklist:

  • I am merging into next because this is new documentation that has a matching pull-request in esphome as linked above.
    or

  • I am merging into current because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.

  • Link added in /components/index.rst when creating new documents for new components or cookbook.

Copy link

netlify bot commented Aug 12, 2025

Deploy Preview for esphome ready!

Name Link
🔨 Latest commit d794389
🔍 Latest deploy log https://app.netlify.com/projects/esphome/deploys/689bc5c81a5522000816fffe
😎 Deploy Preview https://deploy-preview-5234--esphome.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@@ -161,6 +161,8 @@ LWIP (Lightweight IP) behavior. Some options improve performance while others sa
improves socket operation performance by 20-200% but may reduce multi-threaded scalability. Defaults to ``true``.
- **enable_lwip_check_thread_safety** (*Optional*, boolean): Enable LWIP thread safety checks to detect incorrect usage of
the TCP/IP stack from multiple threads. This helps catch thread safety issues when core locking is enabled. Defaults to ``true``.
- **enable_lwip_tcp_sack** (*Optional*, boolean): Enable TCP selective acknowledgments
to improve performance on lossy or high latency networks. Defaults to ``true``.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The documentation should mention that the option is framework-dependent (only applies when using esp-idf)

Copy link
Contributor Author

@RubenKelevra RubenKelevra Aug 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, yeah, sorry forgot that.

The other lwip options should get the same treatment, though.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, never mind. I was missing that context. The header for the entire LWIP options section already says "LWIP Optimization Options (ESP-IDF only):" so there is no need to add notes on the specific options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants