From: Dinesh Kumar <raidinesh@utexas.edu>
To: users@dpdk.org
Subject: How to use --vdev Options for ./dpdk-l3fwd?
Date: Mon, 10 Apr 2023 18:47:59 -0400 [thread overview]
Message-ID: <CANq-2AG__Thox8_qoH3BUEnpA0HZ-A-jNwQxGtfQhEeiX3Uw9A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1433 bytes --]
Hi There,
I am new to the DPDK example and having issue with using --vdev options
for DPDK example and it is throwing the below error.
./dpdk-l3fwd --log-level *:debug -c f -n 4 -- -p 0x3 --vdev
'net_pcap0,rx_pcap=input.pcap,tx_pcap=output.pcap'
-----------------------
iavf_check_api_version(): Peer is supported PF host
iavf_read_msg_from_pf(): Can't read msg from AQ
iavf_read_msg_from_pf(): AQ from pf carries opcode 3, retval 0
iavf_dev_alarm_handler(): ICR01_ADMINQ is reported
iavf_handle_pf_event_msg(): VIRTCHNL_EVENT_LINK_CHANGE event
iavf_handle_virtchnl_msg(): adminq response is received, opcode = 26
EAL: lib.telemetry log level changed from disabled to debug
TELEMETRY: Attempting socket bind to path
'/var/run/dpdk/rte/dpdk_telemetry.v2'
TELEMETRY: Socket creation and binding ok
TELEMETRY: Telemetry initialized ok
TELEMETRY: No legacy callbacks, legacy socket not created
*./dpdk-l3fwd: unrecognized option '--vdev'*
./dpdk-l3fwd [EAL options] -- -p PORTMASK [-P] [--lookup] --config
(port,queue,lcore)[,(port,queue,lcore)] [--rx-queue-size NPKTS]
[--tx-queue-size NPKTS] [--eth-dest=X,MM:MM:MM:MM:MM:MM] [--max-pkt-len
PKTLEN] [--no-numa] [--hash-entry-num] [--ipv6] [--parse-ptype]
[--per-port-pool] [--mode] [--eventq-sched] [--event-vector
[--event-vector-size SIZE] [--event-vector-tmo NS]] [-E] [-L]
please let me know if I am missing some options that need to be added with
--vdev
Thanks,
Dinesh Kumar
[-- Attachment #2: Type: text/html, Size: 1621 bytes --]
next reply other threads:[~2023-04-10 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 22:47 Dinesh Kumar [this message]
2023-04-10 23:08 ` Stephen Hemminger
2023-04-11 16:51 ` Dinesh Kumar
2023-04-11 18:02 ` Stephen Hemminger
2023-04-11 20:13 ` Dinesh Kumar
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=CANq-2AG__Thox8_qoH3BUEnpA0HZ-A-jNwQxGtfQhEeiX3Uw9A@mail.gmail.com \
--to=raidinesh@utexas.edu \
--cc=users@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).