From: Marco Chiappero <marco@absence.it>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Any ideas how to stop DPDK from banning me from the box.
Date: Fri, 19 Jul 2013 10:34:35 +0200 [thread overview]
Message-ID: <51E8FA1B.2080002@absence.it> (raw)
In-Reply-To: <51E8E6B0.8050602@gmail.com>
Il 19/07/2013 09:11, Dmitry Vyal ha scritto:
> Hi Marco,
>
> thanks for posting the example I carefully composed mine using your as a
> basis and, guess, all works I don't have the exact cmdline I issued
> yesterday. Looks like bash didn't have a chance to save history But I
> guess I put all the -b options after the -- delimiter so they weren't
> parsed by rte_eal_init. You saved me a day!
Hi Dmitry,
I'm glad I could help!
By the way, you can also avoid using the PMD igb driver entirely if you
don't need it (I don't as I just care about 10Gbit interfaces, but since
you have lots of 82576 NICs I'm not that sure); just change your compile
configuration, either the default one or a custom one (depending on what
you are using):
pino:~/dpdk-1.2.3r4 -> grep IGB config/defconfig_x86_64-marco-linuxapp-gcc
# Compile burst-oriented IGB PMD driver
CONFIG_RTE_LIBRTE_IGB_PMD=n
CONFIG_RTE_LIBRTE_IGB_DEBUG_INIT=n
CONFIG_RTE_LIBRTE_IGB_DEBUG_RX=n
CONFIG_RTE_LIBRTE_IGB_DEBUG_TX=n
CONFIG_RTE_LIBRTE_IGB_DEBUG_TX_FREE=n
CONFIG_RTE_LIBRTE_IGB_DEBUG_DRIVER=n
As you can see here I keep using the kernel space igb driver:
pino:~/dpdk-1.2.3r4 -> lspci -kD | grep -A 2 -i ether
0000:02:00.0 Ethernet controller: Mellanox Technologies MT26448
[ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0)
Subsystem: Mellanox Technologies Device 0016
Kernel driver in use: mlx4_core
0000:03:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
Subsystem: Intel Corporation Ethernet Server Adapter X520-2
Kernel driver in use: igb_uio
0000:03:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
Subsystem: Intel Corporation Ethernet Server Adapter X520-2
Kernel driver in use: igb_uio
0000:04:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
Subsystem: Intel Corporation Ethernet Server Adapter X520-2
Kernel driver in use: igb_uio
0000:04:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
Subsystem: Intel Corporation Ethernet Server Adapter X520-2
Kernel driver in use: igb_uio
0000:05:00.0 Ethernet controller: Intel Corporation 82576 Gigabit
Network Connection (rev 01)
Subsystem: Super Micro Computer Inc Device 10c9
Kernel driver in use: igb
0000:05:00.1 Ethernet controller: Intel Corporation 82576 Gigabit
Network Connection (rev 01)
Subsystem: Super Micro Computer Inc Device 10c9
Kernel driver in use: igb
Regards,
Marco
next prev parent reply other threads:[~2013-07-19 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 15:42 Dmitry Vyal
2013-07-18 15:53 ` Patrick Mahan
2013-07-18 15:59 ` Marco Chiappero
2013-07-19 7:11 ` Dmitry Vyal
2013-07-19 8:34 ` Marco Chiappero [this message]
2013-07-19 14:30 ` Antti Kantee
2013-07-19 16:35 ` Vincent JARDIN
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=51E8FA1B.2080002@absence.it \
--to=marco@absence.it \
--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).