From: Dmitry Vyal <dmitryvyal@gmail.com>
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 11:11:44 +0400 [thread overview]
Message-ID: <51E8E6B0.8050602@gmail.com> (raw)
In-Reply-To: <51E810C4.1090207@absence.it>
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!
>
> 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-19 7:11 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 [this message]
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=51E8E6B0.8050602@gmail.com \
--to=dmitryvyal@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).