-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add headroom policy and assembler for dedicated #124
add headroom policy and assembler for dedicated #124
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #124 +/- ##
==========================================
- Coverage 51.30% 50.85% -0.45%
==========================================
Files 318 387 +69
Lines 32418 36999 +4581
==========================================
+ Hits 16632 18817 +2185
- Misses 13840 16056 +2216
- Partials 1946 2126 +180
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
6536051
to
63e3f24
Compare
) | ||
|
||
type HeadroomAssembler interface { | ||
GetHeadroom() (resource.Quantity, error) | ||
} | ||
|
||
type InitFunc func(conf *config.Configuration, extraConf interface{}, regionMap *map[string]region.QoSRegion, | ||
reservedForReclaim *map[int]int, numaAvailable *map[int]int, nonBindingNumas *machine.CPUSet, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why should we use map pointer here? does it mean that we will depend on this pointer to get the latest version for the map (which is not proper actually)? why not put those info in metacache?
68a739f
to
6ccf5fe
Compare
What type of PR is this?
Enhancements
What this PR does / why we need it:
Add a headroom policy based on load and headroom assembler for scene with dedicated containers.
Which issue(s) this PR fixes:
Special notes for your reviewer: