[dpdk-dev] [PATCH v1 0/6] ethdev: allow unknown link speed

[Ferruh Yigit]

On 5/7/2020 2:55 PM, Ivan Dyukov wrote:
> 07.05.2020 13:31, Thomas Monjalon пишет:
>> 07/05/2020 10:53, Ivan Dyukov:
>>> 06.05.2020 20:42, Ferruh Yigit пишет:
>>>> On 4/27/2020 10:57 AM, Ivan Dyukov wrote:
>>>>> This is initial patchset which introduces UNKNOWN speed to dpdk
>>>>> applications. Also it contains changes related to printf formating.
>>>>> Patchset contains changes for app/ and doc/ folders.
>>>>> examples/ folder will be provided later.
>>>>>
>>>>>
>>>> Also I can see there are some physical PMDs that are using 'ETH_SPEED_NUM_NONE'
>>>> as unknown, can we fix them as part of this set?
>>>>
>>> Initially, we had a plan to use UNKNOWN only for virtual devices.
>>>
>>> Thomas, could you please comment this?
>> No I think UNKNOWN must be used also for HW devices which are not able
>> to provide a speed value.
>>
>> In mlx5 case, it can be used to return the link status (up/down)
>> even if speed query is failing (it happens with buggy kernel version).
>>
> Ok.  Is ETH_SPEED_NUM_NONE still needed then?  could it be replaced by 
> UNKNOWN everywhere?

It is needed, please don't replace it.

For example when the link is down, device speed is 'ETH_SPEED_NUM_NONE', but
when the link is up but driver doesn't know the speed, for some reason, device
speed is 'ETH_SPEED_NUM_UNKNOWN'.

First patch says 'ETH_SPEED_NUM_UNKNOWN' is for two cases:
	- speed is not known by the driver
	- device is virtual

We are talking about first case above.