Implement hash table inspector #630
Merged
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.
I created another tool in
toolscalleddpservice-inspect. It's another secondary process that reads shared memory and dumps the hash table entries.Almost all tables can be inspected fully, with the exception of table of interfaces which uses static memory for the port structures instead of allocated hugepage memory. To inspect this table, dpservice would need to allocate the port table in advance.
I also did not implement virtual service table inspection as virtual services actually create one hash-table per virtual service with 64k entries (ports) and that is a completely different design than the current implementation. Moreover the data is also not shared in hugepage memory.
This tool has already been used to find bugs and is successfully running in OSC.
Fixes #498