-
Notifications
You must be signed in to change notification settings - Fork 49
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
Support VF interrupt binding to specified CPU #10
Comments
yes, that is great idea to work on. |
@hustcat Can we have a discussion on this implementation ? |
@hustcat @rkamudhan We are currently exploring this feature in our PoC - maybe we can collaborate together on it? |
Yeah, @lmdaly @rkamudhan Do you have any detailed implementation? |
We should think how to coordinate with k8s, and k8s don't support cpuset for container now. Ref k8s #10570. |
@hustcat the new native CPU Manager in Kubernetes uses cpusets to assigns cores at a container level. It should be an alpha feature in K8s 1.8. |
Here's the stable link to the proposal (it has been merged): CPU manager |
Here's a general top-level issue to help track work (since we need more than just coordination with CNI): kubernetes/kubernetes#49964 |
CNI spec support ordered plugin chaining, we can write a interrupt binding plugin to bind interrupt of VF to assigned CPU. @rkamudhan
The text was updated successfully, but these errors were encountered: