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

Review/refactor datapath to avoid unnecessary allocations and resource leakage #24

Open
vladimirvivien opened this issue Sep 5, 2022 · 0 comments

Comments

@vladimirvivien
Copy link
Owner

Now that the control portion of the API seems to be stable. It is time to go back into the datapath API to do some remodeling. This started with #22 . It appears that some early decisions in that portion of the code needs some refactoring to ensure better stability and avoid resource leakage.

@vladimirvivien vladimirvivien changed the title Refactor datapath to avoid unnecessary allocations Review/refactor datapath to avoid unnecessary allocations and resource leakage Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant