-
Notifications
You must be signed in to change notification settings - Fork 149
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
Revert mtu #316
Revert mtu #316
Conversation
Pull Request Test Coverage Report for Build 12732442456Details
💛 - Coveralls |
@@ -225,6 +225,18 @@ func (s *sriovManager) ReleaseVF(conf *sriovtypes.NetConf, podifName string, net | |||
} | |||
} | |||
|
|||
// reset MTU for VF device until if the MTU was captured in the cache | |||
if conf.OrigVfState.MTU != 0 { | |||
logging.Debug("Reset VF device MTU", |
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.
Print out the desired MTU value (conf.OrigVfState.MTU
).
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.
done
@SchSeba why do we need to reset VF MTU if we never set it in the CNI ? currently we save the PF or VF mtu in conf to report it in cni results but never set it |
we introduce this feature in the cni to handle cases where a pod that used the vf has net_admin and change the MTU on the VF. when that po is removed the VF will go back to the host and be available for a new pod to run but when that VF gets allocated to the pod it will remain with an unexpected MTU. Signed-off-by: Sebastian Sch <[email protected]>
Hi @adrianchiris, let me know if that works for you |
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.
usecase understood. LGTM
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.
LGTM
we introduce this feature in the cni to handle cases where a pod that used the vf has net_admin and change the MTU
on the VF.
when that pod is removed the VF will go back to the host and be available
for a new pod to run but when that VF gets allocated to the pod it will
remain with an unexpected MTU.