Open wawa0210 opened 8 months ago
@klueska @elezar friendly ping
Hi. Sorry @wawa0210.
We have been focussed on other development for the past couple of weeks.
It may make sense to not trigger the nvidia-smi
call if sharing is not set. Would you be willing to create a PR with a proposal for us to review?
It's called everytime at the moment to ensure that when sharing is not set, that it gets set to the default time slice (in case it had been set to something else previously).
A better check might be to ensure that the architecture is Kepler+ before attempting to make the call.
A better check might be to ensure that the architecture is Kepler+ before attempting to make the call.
It seems that no accurate documentation has been found describing which architectures support time slice settings,Is there accurate information available for reference?
Hi. Sorry @wawa0210.
We have been focussed on other development for the past couple of weeks.
It may make sense to not trigger the
nvidia-smi
call if sharing is not set. Would you be willing to create a PR with a proposal for us to review?
okk
When I ran DRA on the Tesla P4 node, I found that the pod failed to start.
environment
K8s version: v1.27.5 k8s-dra-driver: latest branch main
what happened
Deployment pod in Tesla P4 environment occupies one card and reports an error
dig found that when the GPU is set to not share,
nvidia-smi compute-policy -i uuid --set-timeslice 0
will still be set, but Tesla P4 does not support this command, so an error is reportedcode ref https://github.com/NVIDIA/k8s-dra-driver/blob/702a05b98b145bdd7e2beb8543fa24c69e2e7330/cmd/nvidia-dra-plugin/sharing.go#L99-L120
Steps to reproduce
Test yaml information
other information
NAS info
In this case, if sharing is not set, is it possible not to call the setTimeSlice method?
Looking forward to hearing from the community and then I can try to fix it