Skip to content

RDMA cannot be disabled #919

@e-minguez

Description

@e-minguez

#666 (in fact #799) made a change on how RDMA is being managed with the operator. Basically it just allows to be "shared" or "exclusive". There are some scenarios that benefit of not having RDMA active, such as trying to reduce queues using 'ethtool -L {interface} combined "XX"' to avoid vector exhaustion. However the module complains as "ice XXX YY Cannot change channels when RDMA is active".
Disabling RDMA by blacklisting the module and disabling RDMA service then makes SRIOV checking for RDMA service and failing as:

2025-07-23T08:05:46.673817651Z ERROR daemon/writer.go:142 DiscoverRDMASubsystem(): failed to get RDMA subsystem mode {"error": "protocol not supported"}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions