-
Notifications
You must be signed in to change notification settings - Fork 339
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
proposal: support pod customizing numa policy #1910
proposal: support pod customizing numa policy #1910
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1910 +/- ##
==========================================
+ Coverage 67.23% 67.47% +0.24%
==========================================
Files 407 420 +13
Lines 45644 46858 +1214
==========================================
+ Hits 30687 31617 +930
- Misses 12741 12938 +197
- Partials 2216 2303 +87
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
a00c39c
to
3a0b640
Compare
BTW, please fix DCO by git commit -s. |
Signed-off-by: KunWuLuan <kunwuluan@gmail.com>
90b91d5
to
5f882f4
Compare
Signed-off-by: KunWuLuan <kunwuluan@gmail.com>
/lgtm |
Signed-off-by: KunWuLuan <kunwuluan@gmail.com>
ab1975c
to
23f7ce6
Compare
/lgtm |
@hormes Hi, is there any questions for this proposal? If not we can start to implement the new feature. Please take a look if you have time, thanks. |
LGTM. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hormes The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
c64c01e
into
koordinator-sh:main
Ⅰ. Describe what this PR does
Introduce new api for pod level numa topology policy. With the new api, users can specify numa topology policy for each
pod, so that pods that are more sensitive to latency can decide how they need to be orchestrated, rather than being passively
scheduled according to the numa topology policy on the node.
Ⅱ. Does this pull request fix one issue?
Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist
make test