Hi Francesco, You're on the right track. Please note that struct rte_eth_dev_info also has max_rx_queues field - maximum number of RX queues the NIC supports.
Regards, Andriy On Tue, Oct 27, 2015 at 10:59 AM, Montorsi, Francesco <fmontorsi at empirix.com> wrote: > Hi, > Just as reference for other DPDK users: the solution to the problem is simple: > > rte_eth_dev_info_get (uint8_t port_id, struct rte_eth_dev_info *dev_info) > > returns a dev_info structure that contains "driver_name"... > > HTH, > Francesco > > > >> -----Original Message----- >> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Montorsi, >> Francesco >> Sent: luned? 26 ottobre 2015 15:18 >> To: dev at dpdk.org >> Subject: [dpdk-dev] how to get driver name for a given port ID >> >> Hi all, >> >> Is there an API to retrieve the driver name for a certain port ID before >> calling >> rte_eth_dev_configure()? >> >> My use case is: I'm trying to call rte_eth_dev_configure() with nb_rx_q=4 >> and found that this works for ixgbe driver but it doesn't for "rte_em_pmd" >> (1Gbps device): >> >> ERROR HwEmulDPDKPort::init() rte_eth_dev_configure: err=-22, port=0: >> Unknown error -22 >> EAL: PCI device 0000:03:00.0 on NUMA socket 0 >> EAL: remove driver: 8086:105e rte_em_pmd >> EAL: PCI memory unmapped at 0x7feb40000000 >> EAL: PCI memory unmapped at 0x7feb40020000 >> >> So, for those devices I want to use nb_rx_q=1... >> >> Thanks, >> >> Francesco Montorsi > -- Andriy Berestovskyy
