Skip to content
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

Update buffer allocation strategy and maximum buffer size when using TCP as transport #29698

Closed
pidarped opened this issue Oct 10, 2023 · 1 comment

Comments

@pidarped
Copy link
Contributor

Feature description

Depending on the transport choice, the node would have to be able to allocate buffers appropriately. When TCP is supported, buffer allocation would be done from the heap. That choice is made at compile time. However, the max size of the heap-allocated buffer would differ based on whether the node is using MRP or TCP underneath, at run time. We would need a dynamic way to choose that max buffer size allocation so that a larger allocation can be made from the heap when using TCP.

Platform

core

Platform Version(s)

No response

Anything else?

No response

@pidarped
Copy link
Contributor Author

Fixed by #33308

@github-project-automation github-project-automation bot moved this from Todo to Done in [Device Type] Cameras Aug 29, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in [Feature] TCP Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Archived in project
Archived in project
3 participants