Fix #178 - extract numa info #179
Merged
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
lars-t-hansen
force-pushed
the
w-178-numa-info
branch
from
f81502f
to
5c655a3
Compare
|
I should probably add an integration test too now that there is a command line option. |
|
Thank you! |
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.
Currently a WIP, decoding /proc/stat and outlining various representation strategies for the data to make them compact. There are endless possibilities, but a base-45 variable-length delta-from-minimum encoding with separators represented as distinguished leading digits is probably about as compact as more standard encodings (eg uleb64+base64), and simpler than the latter.