From: Kevin Wilson <wkevils@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] dpdk pcap in testpmd - not working in dpdk 16.11
Date: Sat, 31 Dec 2016 11:19:17 +0200 [thread overview]
Message-ID: <CAGXs5wWeAFByHeF48kkdeqaM5v1_PeEqz4QSEda=CqTZ4kj-XA@mail.gmail.com> (raw)
Hi,
I am trying to read packets from one pcap file and write them to
another pcap file,
according to the example in:
http://dpdk.org/doc/guides/nics/pcap_ring.html
The code is built with support for pmd pcap (I have in build/.config:
CONFIG_RTE_LIBRTE_PMD_PCAP=y)
In dpdk-16.04 this works:
I am running:
./build/app/testpmd -c '0x3' -n 4 --vdev
'eth_pcap0,rx_pcap=96pings.pcap,tx_pcap=file_tx.pcap' --
--port-topology=chained
and after pressing enter I see
+++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
RX-packets: 96 RX-dropped: 0 RX-total: 96
TX-packets: 96 TX-dropped: 0 TX-total: 96
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
and a file named "file_tx.pcap" is generated, and it has the exact
size of the input file, 96pings.pcap.
Next I tried with dpdk 16.11 and it fails to copy the file, but
without an error message.
As opposed to the previous invocation, please note the change to
"net_pcap0", according to the the doc, which is not supported in
16.04.
./build/app/testpmd -c '0x3' -n 4 --vdev
'net_pcap0,rx_pcap=96pings.pcap,tx_pcap=file_tx.pcap' --
--port-topology=chained
What I see is:
...
+++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
RX-packets: 0 RX-dropped: 0 RX-total: 0
TX-packets: 0 TX-dropped: 0 TX-total: 0
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
And
ls -al *.pcap
shows that the file_tx.pcap size is only 24 bytes (as opposed to the
input file, 96pings.pcap, which is
10776 bytes).
Any ideas ? is it a BUG of 16.11 ? can somebody check this sequence in
16.11 with some arbitrary pcap input file?
Regards,
Kevin
reply other threads:[~2016-12-31 9:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAGXs5wWeAFByHeF48kkdeqaM5v1_PeEqz4QSEda=CqTZ4kj-XA@mail.gmail.com' \
--to=wkevils@gmail.com \
--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).