From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0.salzburgresearch.at (mx0.salzburgresearch.at [78.104.175.164]) by dpdk.org (Postfix) with ESMTP id 961055697 for ; Thu, 6 Aug 2015 14:46:55 +0200 (CEST) X-Virus-Scanned: by Salzburg Research on mx0.salzburgresearch.at DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=salzburgresearch.at; s=srfg; t=1438865215; bh=oP/QGihLAvdvLQDaX0b8yijWKCpv9WrVlCYomILvQ7U=; h=To:From:Subject:Date:From; b=cwSrUAKfBT9siO5f3lxyxEW1y+eMYQBfKcoylg9shVcGB01zkaJ1TL9MHj5ws6F+7 aV6Z+GZxW7AQ/BU5q7GR5snxUC7vyXIwtWeBHoTx+jM2IbgeaOBeFcVaZT1xiNr0oH 5/sU6rGii3jr3UDze0tAUCD4WtYhCUXz+wILRT3E= Received: from mail01.salzburgresearch.at (mail01.salzburgresearch.at [172.16.0.31]) by mx0.salzburgresearch.at (Postfix) with ESMTPS id 04866200EC4 for ; Thu, 6 Aug 2015 14:46:54 +0200 (CEST) Received: from [172.16.96.142] (anc42.salzburgresearch.at [172.16.96.142]) by mail01.salzburgresearch.at (Postfix) with ESMTPSA id E02075196 for ; Thu, 6 Aug 2015 14:46:53 +0200 (CEST) To: dev@dpdk.org From: Stefan Binna Message-ID: <55C3573D.9060308@salzburgresearch.at> Date: Thu, 6 Aug 2015 14:46:53 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] TX-packet counter increased when no packets were actually sent X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Aug 2015 12:46:55 -0000 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.