[dpdk-dev] [PATCH] ethdev: The users could get device types now

Agree with NACK. This type of string matching won't scale. THe better way is to encapsulate required behavior in feature flags. I started that with drv_flags, and that seems natural home for such device specific stuff. On Sun, Sep 28, 2014 at 5:36 AM, Neil Horman wrote: > On Sun, Sep 28, 2014 at

[dpdk-dev] [PATCH] ethdev: The users could get device types now

As different PMDs support different features, application may want to know the NIC type of a port, then decide how to use that port. Add a new field in struct rte_eth_dev, users are able to get device type now. Signed-off-by: Ding Heng --- lib/librte_ether/rte_ethdev.c | 32 +

[dpdk-dev] [PATCH] ethdev: The users could get device types now

On Sun, Sep 28, 2014 at 11:27:16AM +0800, Ding Heng wrote: > As different PMDs support different features, application may want > to know the NIC type of a port, then decide how to use that port. > Add a new field in struct rte_eth_dev, users are able to get > device type now. > > Signed-off-by: D

[dpdk-dev] [PATCH] ethdev: The users could get device types now

Acked-by: Helin Zhang > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Ding Heng > Sent: Sunday, September 28, 2014 11:27 AM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH] ethdev: The users could get device types now > > As d