DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] [RFC] some questions for speed_capa usage
@ 2021-01-18 10:27 oulijun
  2021-01-18 11:23 ` Ferruh Yigit
  0 siblings, 1 reply; 3+ messages in thread
From: oulijun @ 2021-01-18 10:27 UTC (permalink / raw)
  To: dev; +Cc: linuxarm, lihuisong (C)

Hi,


The 'speed_capa' will be reported in rte_eth_dev_info_get API. How 
should users use the field?

1) The driver reports only the capabilities supported by the NIC, and 
users only obtain the capabilities.
Maybe, there is a case that a rate bit in 'speed_capa' is not supported 
by the current transmission medium,
such as, copper cable optical modules and optical interface modules.

2) The field is used only to inform users of the speed_capa supported by 
the current transmission medium.
And users set the fixed speed or auto-negotiation by using 'link_speeds' 
according to the field.

According to the existing implementations of all drivers, it seems that 
both of the above behaviors exist.

How should we report and use it?


Thanks

Lijun Ou


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-dev] [RFC] some questions for speed_capa usage
  2021-01-18 10:27 [dpdk-dev] [RFC] some questions for speed_capa usage oulijun
@ 2021-01-18 11:23 ` Ferruh Yigit
  2021-01-23  9:06   ` oulijun
  0 siblings, 1 reply; 3+ messages in thread
From: Ferruh Yigit @ 2021-01-18 11:23 UTC (permalink / raw)
  To: oulijun, dev; +Cc: linuxarm, lihuisong (C)

On 1/18/2021 10:27 AM, oulijun wrote:
> Hi,
> 
> 
> The 'speed_capa' will be reported in rte_eth_dev_info_get API. How should users 
> use the field?
> 
> 1) The driver reports only the capabilities supported by the NIC, and users only 
> obtain the capabilities.
> Maybe, there is a case that a rate bit in 'speed_capa' is not supported by the 
> current transmission medium,
> such as, copper cable optical modules and optical interface modules.
> 
> 2) The field is used only to inform users of the speed_capa supported by the 
> current transmission medium.
> And users set the fixed speed or auto-negotiation by using 'link_speeds' 
> according to the field.
> 
> According to the existing implementations of all drivers, it seems that both of 
> the above behaviors exist.
> 
> How should we report and use it?
> 

Hi Lijun,

When the driver reports the capabilities supported by the NIC, we tend to mark 
this feature as partially supported.

The expectation is the driver report the capability for the current 
configuration, the PHY/FW/transmission medium, whatever it is.

Driver should return the current supported values so that application can select 
one, as you said.

Regards,
ferruh

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-dev] [RFC] some questions for speed_capa usage
  2021-01-18 11:23 ` Ferruh Yigit
@ 2021-01-23  9:06   ` oulijun
  0 siblings, 0 replies; 3+ messages in thread
From: oulijun @ 2021-01-23  9:06 UTC (permalink / raw)
  To: Ferruh Yigit, dev; +Cc: linuxarm, lihuisong (C)



在 2021/1/18 19:23, Ferruh Yigit 写道:
> On 1/18/2021 10:27 AM, oulijun wrote:
>> Hi,
>>
>>
>> The 'speed_capa' will be reported in rte_eth_dev_info_get API. How 
>> should users use the field?
>>
>> 1) The driver reports only the capabilities supported by the NIC, and 
>> users only obtain the capabilities.
>> Maybe, there is a case that a rate bit in 'speed_capa' is not 
>> supported by the current transmission medium,
>> such as, copper cable optical modules and optical interface modules.
>>
>> 2) The field is used only to inform users of the speed_capa supported 
>> by the current transmission medium.
>> And users set the fixed speed or auto-negotiation by using 
>> 'link_speeds' according to the field.
>>
>> According to the existing implementations of all drivers, it seems 
>> that both of the above behaviors exist.
>>
>> How should we report and use it?
>>
> 
> Hi Lijun,
> 
> When the driver reports the capabilities supported by the NIC, we tend 
> to mark this feature as partially supported.
> 
> The expectation is the driver report the capability for the current 
> configuration, the PHY/FW/transmission medium, whatever it is.
> 
> Driver should return the current supported values so that application 
> can select one, as you said.
> 
Thank you for your answer. I see.
> Regards,
> ferruh
> .
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-01-23  9:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-18 10:27 [dpdk-dev] [RFC] some questions for speed_capa usage oulijun
2021-01-18 11:23 ` Ferruh Yigit
2021-01-23  9:06   ` oulijun

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git