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

Prevent packet pool starvation when waiting for nh resolution #110

Open
david-marchand opened this issue Dec 13, 2024 · 1 comment
Open

Comments

@david-marchand
Copy link
Member

Packets requiring some arp/ndp resolution for nexthop are currently stored in a per interface (fixed size) "hold queue".
In theory, doing so exposes grout to packet starvation if the packet pool size is < sum of all "hold queue" sizes since it is then possible to store more packets in the "hold queues" and then no packet would be left in the packet pool.

@david-marchand
Copy link
Member Author

One solution would be to have a "control path" packet pool.
Held packets would come from this pool, and would be copied from the original mbuf, returned to the "data path" packet pool.

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