Skip to content

Handling device availability is not consistent #239

@ScottDaniels

Description

@ScottDaniels

During initialisation the number of ports reported by DPDK is checked with what is expected in the config file and errors/warnings are issued based on what is expected vs what is found. If less ports are available than expected a warning is issued and execution continues. If more ports are reported than expected a critical message, indicating abort is to be performed, is written, but the abort doesn't happen.

This section of main.c needs to be examined and cleaned up. My suggestion is to issue a critical error and abort if the number of reported devices does NOT match the number of devices in the config as we have specifically whitelisted all of the devices in the config and if one is missing that is not a state that I think we should continue with.

Code in main.c is about line 1598.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions