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: Thu, 18 Jul 2013 17:59:00 +0200 [thread overview]
Message-ID: <51E810C4.1090207@absence.it> (raw)
In-Reply-To: <51E80CF9.6030005@gmail.com>
Il 18/07/2013 17:42, Dmitry Vyal ha scritto:
> Greetings!
Hi
> [...]
> I connect to the server using ssh through one of gigabit ports.
I do the very same thing and I have no such problem.
> The
> problem is that no matter which cards I blacklist with -b option then
> starting my dpdk application it takes away all the interfaces from the
> kernel and later returns blacklisted ones. This disrupts my ssh session
> and I can no longer connect to the server.
Maybe you are using wrong IDs, verify that.
Here a working example:
pino:~/dpdk-1.2.3r4 ~> lspci | grep -i ethernet
02:00.0 Ethernet controller: Mellanox Technologies MT26448 [ConnectX EN
10GigE, PCIe 2.0 5GT/s] (rev b0)
03:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
03:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
04:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
04:00.1 Ethernet controller: Intel Corporation 82599EB 10-Gigabit
SFI/SFP+ Network Connection (rev 01)
05:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network
Connection (rev 01)
05:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network
Connection (rev 01)
pino:~/dpdk-1.2.3r4 ~> sudo build/app/testpmd -c 0xf -n 3 -r 1 -b
0000:05:00.0 -b 0000:05:00.1
EAL: coremask set to f
...
Initializing port 0... done: Link Down
Initializing port 1... done: Link Down
Initializing port 2... done: Link Up - speed 10000 Mbps - full-duplex
Initializing port 3... done: Link Up - speed 10000 Mbps - full-duplex
No commandline core given, start packet forwarding
io packet forwarding - CRC stripping disabled - packets/burst=16
nb forwarding cores=1 - nb forwarding ports=4
RX queues=1 - RX desc=128 - RX free threshold=0
RX threshold registers: pthresh=8 hthresh=8 wthresh=4
TX queues=1 - TX desc=512 - TX free threshold=0
TX threshold registers: pthresh=36 hthresh=0 wthresh=0
TX RS bit threshold=0
Press enter to exit
[ssh is still up]
Regards,
Marco
next prev parent reply other threads:[~2013-07-18 15:58 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 [this message]
2013-07-19 7:11 ` Dmitry Vyal
2013-07-19 8:34 ` Marco Chiappero
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=51E810C4.1090207@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).