examples/ipsec-secgw: fix bug of rte_eth_add_rx_callback failure in single lcore scenario #75
Conversation
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
…ingle lcore scenario
dpdk-replication
force-pushed
the
main
branch
from
eb5cf3d to
39fbd37
Compare
|
DPDK does not use the PR model, please see doc/guides/contributing/patches.rst |
dpdk-replication
force-pushed
the
main
branch
from
f5e074d to
c164c58
Compare
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.
In the scenario of multiple ports and single lcore, rte_eth_add_rx_callback will fail because the queueid here is used incorrectly and rx_queueid should be used.