Merged
Conversation
The log entry below doesn't have an equivalent for IPv6 and it's ONLY logged when 1. The number of IPv4 packets that rte_eth_rx_burst() returns is not multiple of 4; and 2. The destination of the last packets on the array of returned packets is not on the LPM table of IPv4. The multiple of 4 emerges from the use of rte_lpm_lookupx4(). So there might be 1, 2, or 3 last packets that could trigger the log entry. Moreover, adding the log entry to all other conditions (i.e. multiple of 4 and IPv6) is not helpful because all packets whose destinations are not in the FIB are passed to the filter subsystem to be directed to another block. And the filter system already has a log entry for unmatched packets. THIS PATCH REMOVES THE FOLLOWING LOG ENTRY: GATEKEEPER GK: process_pkts_front could not find FIB entry when processing incoming IPv4 flow
Owner
Author
|
Tested on the XIA1 server. |
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
1 participant
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.
The log entry below doesn't have an equivalent for IPv6 and it's ONLY logged when
rte_eth_rx_burst()returns is not multiple of 4; andThe multiple of 4 emerges from the use of
rte_lpm_lookupx4(). So there might be 1, 2, or 3 last packets that could triggerthe log entry.
Moreover, adding the log entry to all other conditions (i.e. multiple of 4 and IPv6) is not helpful because all packets whose destinations are not in the FIB are passed to the filter subsystem to be directed to another block. And the filter system already has a log entry for unmatched packets.
THIS PATCH REMOVES THE FOLLOWING LOG ENTRY:
GATEKEEPER GK: process_pkts_front could not find FIB entry when processing incoming IPv4 flow