From: Sergey Mironov <grrwlf@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] i211 controller with 0 queues per port
Date: Thu, 4 Sep 2014 11:16:53 +0400 [thread overview]
Message-ID: <CAMOkk_Y0RePg3__EpQA_863ExXVVAerHc+bedjhMR7_wp0SiGw@mail.gmail.com> (raw)
2014-08-26 13:18 GMT+04:00 Sergey Mironov <grrwlf@gmail.com>:
> Hi.
>
> I've got a SCB-8973 machine equipped with i212 network controller (6
> ports). My dpdk application (see the code snippet below) returns zeros
> for both dev_info.max_tx_queues and dev_info.max_rx_queues
>
> Have anybody got an experience of addressing this problem?
>
> Regards,
> Sergey
>
>
>
> for (portid = 0; portid < nb_ports; portid++) {
>
> struct rte_eth_dev_info di;
> rte_eth_dev_info_get(portid, &di);
>
> ELOG_INFO(MAIN, "%-6d %-6d %-6d", portid, di.max_tx_queues,
> di.max_rx_queues);
> }
Hi! I have got an update for my "i212 problem". First of all, I found
that I have made a mistake. My controller is named i211, not i212 :)
Next, i211 controller is controlled by the lib_pmd_e1000 driver.
Unfortunately, looks like it's support is pure. For example,
igb_ethdev.c contains function eth_igb_infos_get() which should set
number of tx/rx queues supported by the hardware. It contains huge
[switch] but there is no i211 case! That is why I see zeros every time
I try to start this NC. Also, there are few other places which mention
i210, but not mention i211. I've attached a patch which adds necessary
i211 support, but I didn't check it enough to say it is totally
correct. For now I see that it just able to send and receive some
packets.
Could you please review/correct it?
Thanks in advance,
Sergey
next reply other threads:[~2014-09-04 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 7:16 Sergey Mironov [this message]
2014-09-04 8:09 ` Thomas Monjalon
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=CAMOkk_Y0RePg3__EpQA_863ExXVVAerHc+bedjhMR7_wp0SiGw@mail.gmail.com \
--to=grrwlf@gmail.com \
--cc=dev@dpdk.org \
/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).