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

user memory allocation in read and write callbacks #320

Open
AchaInChina opened this issue Nov 28, 2024 · 1 comment
Open

user memory allocation in read and write callbacks #320

AchaInChina opened this issue Nov 28, 2024 · 1 comment
Assignees
Labels

Comments

@AchaInChina
Copy link

hello,I have some suggestions,can we add the last custom allocated memory address to the stream req to help determine whether to automatically reclaim the memory or let the user reclaim it in the read and write callbacks.
@skypjack skypjack self-assigned this Dec 4, 2024
@skypjack skypjack added the triage label Dec 4, 2024
@AchaInChina
Copy link
Author

Hello everyone, in some scenarios, such as IOT gateways, there are many connected devices, 10,000+, and it is a bit wasteful to allocate new memory each time it is received. In session design, each link can be allocated a ring buffer, so that the performance may be better.

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

No branches or pull requests

2 participants