Hi,
I encountered an issue while using dpdk-20.05 in our VMware based VMs: at times, when sysstat data is collected, dpdk signals that some eth interface is down; this happens occasionally; after sysstat data has been collected, eth interface is signaled as up; I was wondering about these lines in '__vmxnet3_dev_link_update' function:

1251 >*******VMXNET3_WRITE_BAR1_REG(hw, VMXNET3_REG_CMD, VMXNET3_CMD_GET_LINK);
1252 >*******ret = VMXNET3_READ_BAR1_REG(hw, VMXNET3_REG_CMD);

Is this atomic? Could this lead to problems if some other module tries to read something else at about the same time and overwrites the command?


Thanks,
Ciprian.