From: Stefan Binna <stefan.binna@salzburgresearch.at>
To: dev@dpdk.org
Subject: [dpdk-dev] TX-packet counter increased when no packets were actually sent
Date: Thu, 6 Aug 2015 14:46:53 +0200 [thread overview]
Message-ID: <55C3573D.9060308@salzburgresearch.at> (raw)
Hi,
I have created a little testbed for DPDK testing.
NIC: Intel Gigabit 82574L (1-port)
The testbed for DPDK has following structure:
1) al40-118 (10.100.40.118/24): DUT running the DPDK application
2) al40-119 (10.100.40.119/24): Used for sending traffic to al40-118
3) al40-111 (10.100.40.111/24): Used to sniff the traffic send on the
network
All three devices are connected via a hub and use the network
10.100.40.1/24.
*Test:* Ping the DUT and review network traffic
At al40-119 an ARP-Table-Entry was created and the device al40-118 was
pinged:
arp -s 10.100.40.118 68:05:ca:37:51:75
ping 10.100.40.118
On al40-118 the application testpmd was started with following parameters:
./x86_64-native-linuxapp-gcc/build/app/test-pmd/testpmd -c 0xf -n 4 -- -i --portmask=0x1 --nb-cores=2 --port-topology=chained
After start of the testpmd application the ports were started and after
a while stopped:
start #wait a while due to testduration
stop
What's interesting is, that the TX-packet counter in the output of the
"stop" command had the same value as the RX-packet counter. But the
actual traffic on the network sniffed with Wireshark only showed the
ping request but never a response on any layer (not even L2).
Sample output of the "stop" command:
Telling cores to stop...
Waiting for lcores to finish...
---------------------- Forward statistics for port 0 ----------------------
RX-packets: 2 RX-dropped: 0 RX-total: 2
TX-packets: 2 TX-dropped: 0 TX-total: 2
----------------------------------------------------------------------------
+++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
RX-packets: 2 RX-dropped: 0 RX-total: 2
TX-packets: 2 TX-dropped: 0 TX-total: 2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Done.
Stopping port 0...done
Could you tell me why the TX-packet counter increased when actually no
packets were sent out to the 10.100.40.1 network or in other words,
where have the packets been sent out?
And is it even possible to set the same port for RX and TX?
Thanks!
Regards, Stefan.
next reply other threads:[~2015-08-06 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 12:46 Stefan Binna [this message]
2015-08-10 10:28 ` Bruce Richardson
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=55C3573D.9060308@salzburgresearch.at \
--to=stefan.binna@salzburgresearch.at \
--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).