pool: add option to disable packet pool #658
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This patch is adding an option named 'no-packet-pool'. If set to yes, the packet pool will not be allocated and instead direct allocation will be used. The default value of the option is 'no' to keep backward compatibility. This option has proven to have a huge impact on some system where the packet pool handling was taking a huge amount of CPU in the spinlock.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch is adding an option named 'no-packet-pool'. If set to
yes, the packet pool will not be allocated and instead direct
allocation will be used. The default value of the option is 'no'
to keep backward compatibility.
This option has proven to have a huge impact on some system where
the packet pool handling was taking a huge amount of CPU in the
spinlock.