Skip to content

fix: Wait until NIC device is initialized and udev rules are applied #193

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 20, 2025
+3 −0
Merged

fix: Wait until NIC device is initialized and udev rules are applied #193

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions entrypoint.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -846,6 +846,9 @@ function restore_sriov_config() {

exec_cmd "echo ${pf_numvfs} >> ${pf_pci_dev_path}/sriov_numvfs"

# Sleep to wait until NIC device is initialized and udev rules are applied
sleep ${BIND_DELAY_SEC}
Copy link
Contributor

@heyvister1 heyvister1 Nov 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit. Should we use additional variable here that by default is equal to BIND_DELAY_SEC?

Copy link
Collaborator Author

@e0ne e0ne Nov 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@heyvister1 Actually, when new devices are registered by the kernel it does bind to driver , that's why I use this variable to not introduce a new one


for vf_record in $(seq 0 1 $((vf_record_idx-1))); do
declare -a mlx_vf_info=(${mlx_vfs_arr[$vf_record]})

Expand Down
Loading