DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] Misuses of dev_info->if_index in embedded drivers.
@ 2020-08-24 15:07 Stephen Hemminger
  2020-08-24 15:18 ` Ferruh Yigit
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Hemminger @ 2020-08-24 15:07 UTC (permalink / raw)
  To: Hemant Agrawal, Sachin Saxena; +Cc: dev, Gagandeep Singh, Akhil Goyal

The use of if_index in some drivers is wrong.
It does not match the user expectation in the documentation.

This code:
dpaa2/dpaa2_ethdev.c:   dev_info->if_index = priv->hw_id;
pfe/pfe_ethdev.c:       dev_info->if_index = internals->id;

Does match:
struct rte_eth_dev_info {
	struct rte_device *device; /** Generic device information */
	const char *driver_name; /**< Device Driver name. */
	unsigned int if_index; /**< Index to bound host interface, or 0 if none.
		Use if_indextoname() to translate into an interface name. */

Also, this code is unnecessary.

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

end of thread, other threads:[~2020-08-24 15:33 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-24 15:07 [dpdk-dev] Misuses of dev_info->if_index in embedded drivers Stephen Hemminger
2020-08-24 15:18 ` Ferruh Yigit
2020-08-24 15:33   ` Hemant Agrawal

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).