Skip to content
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

bug: rdma exlusive handling #603

Merged
merged 1 commit into from
Nov 3, 2024

Commits on Oct 29, 2024

  1. bug: rdma exlusive handling

    In case a RDMA device in exclusive mode is in use
    by a Pod, the DP was not reporting it as a resource
    after DP restart.
    
    Following changes are introduced in RdmaSpec:
    
    - isRdma: in case of no rdma resources,
      check if netlink "enable_rdma" is available.
    - GetRdmaDeviceSpec: the device specs are retrieved
      dynamically and not on discovery stage as before.
    
    Dynamic RDMA specs computation vs on discovery, comes
    to solve following scenario for exlusive mode:
    - Discover RDMA device
    - Allocate to Pod (resources are hidden on host)
    - Restart DP pod
    - Deallocate
    - Reallocate
    
    Fixes k8snetworkplumbingwg#565
    
    Signed-off-by: Fred Rolland <[email protected]>
    rollandf committed Oct 29, 2024
    Configuration menu
    Copy the full SHA
    6af2d20 View commit details
    Browse the repository at this point in the history