Merged
Conversation
After upgrading Gatekeeper's DPDK, Gatekeeper is not booting with bond interfaces. This issue is identified with log entries similar to the one below: memzone eth_p1_q0_rx_ring does not justify the requested attributes The example log entry above and others may differ on the name of the queue that triggers the issue. In the example above, the name of the queue is 'eth_p1_q0_rx_ring'.
This file contains hidden or 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
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.
After upgrading Gatekeeper's DPDK, Gatekeeper is not booting with bond interfaces. This issue is identified with log entries similar to the one below:
memzone eth_p1_q0_rx_ring does not justify the requested attributesThe example log entry above and others may differ on the name of the queue that triggers the issue. In the example above, the name of the queue is
eth_p1_q0_rx_ring.The solution consists in allocating the RX and TX queues on the same NUMA socket to which the underlying Ethernet device is connected; see
configure_queue()edited in this pull request for more details. Gatekeeper was using the NUMA node of the block responsible for the queue.Here is a backtrace when the issue is triggered to serve as a reference: