From: Olivier MATZ <olivier.matz@6wind.com>
To: Shankari Vaidyalingam <shankari.v2k6@gmail.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Need info on --vdev option
Date: Mon, 23 Mar 2015 17:01:42 +0100 [thread overview]
Message-ID: <551038E6.6020006@6wind.com> (raw)
In-Reply-To: <CAGeyXNek9FVYZgjYRf1b816BLBSoYASN7DHkmpLJsy-hUehJpA@mail.gmail.com>
Hi Shankari,
On 03/23/2015 04:54 PM, Shankari Vaidyalingam wrote:
> 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'
>
> [...]
> 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
Please note the position of "--" in your command line. This is
used to separate the arguments of eal and application. As --vdev
is an eal argument, it should go before the "--".
Regards,
Olivier
next prev parent reply other threads:[~2015-03-23 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 15:54 Shankari Vaidyalingam
2015-03-23 16:01 ` Olivier MATZ [this message]
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=551038E6.6020006@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=shankari.v2k6@gmail.com \
/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).