>>> If you don't want rx/tx, don't poll the port.
>>Well, the question is why to add an extra restriction here? >Well, until I start a port, I would expect it to do nothing. >>Probably user deliberately doesn't want to call dev_start() for PF device - >>as he doesn't plan to use it for RX/TX. >>Or might be dev_stop() was called just to do some re-configuration >>(allow to TX scattered packets on the PF queues or so). >>Or dev_start() for PF has not yet been called. >>Why VF should stop working properly because of that? >Why not. I thought I explained it above. Basically it means that you can't stop your PF without forcing to stop all VFs first. And you can't start any of your VFs without starting PF first. I think that adds an unnecessary restrictions and limits systems availability quite significantly. Konstantin
