From: Andriy Berestovskyy <aber@semihalf.com>
To: "Montorsi, Francesco" <fmontorsi@empirix.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] how to get driver name for a given port ID
Date: Tue, 27 Oct 2015 11:26:19 +0100 [thread overview]
Message-ID: <CAOysbxr_rAZ+1F+s7cB9Fj-oBd9xFbuNCGm4ymOgC_zGDQDmyg@mail.gmail.com> (raw)
In-Reply-To: <7a035a46a649429084c708cd2c5f8372@bilemail1.empirix.com>
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@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@dpdk.org] On Behalf Of Montorsi,
>> Francesco
>> Sent: lunedì 26 ottobre 2015 15:18
>> To: dev@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
prev parent reply other threads:[~2015-10-27 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 14:17 Montorsi, Francesco
2015-10-27 9:59 ` Montorsi, Francesco
2015-10-27 10:26 ` Andriy Berestovskyy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOysbxr_rAZ+1F+s7cB9Fj-oBd9xFbuNCGm4ymOgC_zGDQDmyg@mail.gmail.com \
--to=aber@semihalf.com \
--cc=dev@dpdk.org \
--cc=fmontorsi@empirix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).