From: Shankari Vaidyalingam <shankari.v2k6@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Need info on --vdev option
Date: Mon, 23 Mar 2015 21:24:37 +0530 [thread overview]
Message-ID: <CAGeyXNek9FVYZgjYRf1b816BLBSoYASN7DHkmpLJsy-hUehJpA@mail.gmail.com> (raw)
Hi
I'm trying to do a packet capture on the DPDK interface while running l2fwd
sample application and injecting packets from a traffic generator.
I'm getting the below error when I give this command: sudo ./build/l2fw-c
0x03 -n 2 -- -p 0x03 --vdev
'eth_pcap0,tx_pcap=/home/controller/pkt_capt/try.pcap'
Pls let me know if I'm missing something.
I also tried checking the documentation and confirmed that the ordering of
the options is correct.
But still I'm getting this error.
I also tried various combinations like: But none of them worked.
sudo ./build/l2fwd -c 0x03 -n 2 --vdev
'eth_pcap0,tx_pcap=/home/controller/pkt_capt/try.pcap' --p 0x03
sudo ./build/l2fwd -c 0x03 -n 2 --vdev
'eth_pcap0,tx_pcap=/home/controller/pkt_capt/try.pcap' -- -p 0x03
sudo ./build/l2fwd -c 0x03 -n 2 --vdev
'eth_pcap0,tx_pcap=/home/controller/pkt_capt/try.pcap'
sudo ./build/l2fwd -c 0x03 -n 2 --p 0x03 --vdev
'eth_pcap0,tx_pcap=/home/controller/pkt_capt/try.pcap'
sudo ./build/l2fwd -c 0x03 -n 2 -- -p 0x03 --vdev
'eth_pcap0,tx_pcap=/home/controller/pkt_capt/try.pcap'
sudo ./build/l2fwd -c 0x03 -n 2 -- -p 0x03
sudo ./build/l2fwd -c 0x03 -n 2 -- -p 0x03 --vdev
'eth_pcap0,tx_pcap=/home/controller/pkt_capt/try.pcap'
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Support maximum 64 logical core(s) by configuration.
EAL: Detected 2 lcore(s)
EAL: Setting up memory...
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7ff21a200000 (size = 0x200000)
EAL: Ask a virtual area of 0x3ec00000 bytes
EAL: Virtual area found at 0x7ff1db400000 (size = 0x3ec00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7ff1db000000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7ff1dac00000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7ff1da800000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7ff1da400000 (size = 0x200000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7ff1d9e00000 (size = 0x400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7ff1d9a00000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7ff1d9600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7ff1d9200000 (size = 0x200000)
EAL: Requesting 512 pages of size 2MB from socket 0
EAL: TSC frequency is ~2683644 KHz
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
EAL: Master core 0 is ready (tid=1b8d6800)
EAL: Core 1 is ready (tid=d87f8700)
EAL: PCI device 0000:00:08.0 on NUMA socket -1
EAL: probe driver: 8086:100f rte_em_pmd
EAL: PCI memory mapped at 0x7ff21b880000
EAL: PCI device 0000:00:09.0 on NUMA socket -1
EAL: probe driver: 8086:100f rte_em_pmd
EAL: PCI memory mapped at 0x7ff21b860000
EAL: PCI device 0000:00:0a.0 on NUMA socket -1
EAL: probe driver: 8086:100f rte_em_pmd
EAL: 0000:00:0a.0 not managed by UIO driver, skipping
EAL: PCI device 0000:00:11.0 on NUMA socket -1
EAL: probe driver: 8086:100f rte_em_pmd
EAL: 0000:00:11.0 not managed by UIO driver, skipping
./build/l2fwd: unrecognized option '--vdev'
./build/l2fwd [EAL options] -- -p PORTMASK [-q NQ]
-p PORTMASK: hexadecimal bitmask of ports to configure
-q NQ: number of queue (=ports) per lcore (default is 1)
-T PERIOD: statistics will be refreshed each PERIOD seconds (0 to
disable, 10 default, 86400 maximum)
EAL: Error - exiting with code: 1
Cause: Invalid L2FWD arguments
Regards
Shankari.V
next reply other threads:[~2015-03-23 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 15:54 Shankari Vaidyalingam [this message]
2015-03-23 16:01 ` Olivier MATZ
2015-03-23 17:47 ` Shankari Vaidyalingam
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=CAGeyXNek9FVYZgjYRf1b816BLBSoYASN7DHkmpLJsy-hUehJpA@mail.gmail.com \
--to=shankari.v2k6@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).