From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id AE54EA0471 for ; Tue, 16 Jul 2019 11:43:52 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9F0DE1B951; Tue, 16 Jul 2019 11:43:50 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id AB58E3195; Tue, 16 Jul 2019 11:43:46 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jul 2019 02:43:45 -0700 X-IronPort-AV: E=Sophos;i="5.63,497,1557212400"; d="scan'208";a="169882200" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.1.207]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jul 2019 02:43:44 -0700 Date: Tue, 16 Jul 2019 10:43:41 +0100 From: Bruce Richardson To: Nilesh Cc: dev@dpdk.org, users@dpdk.org Message-ID: <20190716094341.GA572@bricha3-MOBL.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) Subject: Re: [dpdk-users] [dpdk-dev] TX-dropped is high while sending custom packet via testpmd app X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" On Tue, Jul 16, 2019 at 03:01:12PM +0530, Nilesh wrote: > Hello, >     we are trying to send packets from the testpmd to another machine with > DPDK running. >     We are building custom packets before sending it on the wire. >     After running the application the TX-dropped is quite high (can be > inferred from following logs : ) > > > $ sudo ./testpmd -c f -w 01:00.1  --   --nb-cores=2 > --eth-peer=0,A4:BF:01:37:23:AB --rxq=1 --txq=1 > > > Port statistics ==================================== >  ######################## NIC statistics for port 0 ######################## >  RX-packets: 1445150    RX-missed: 0          RX-bytes:  86709064 >  RX-errors: 0 >  RX-nombuf:  0 >  TX-packets: 1602045    TX-errors: 0          TX-bytes:  134571780 > >  Throughput (since last show) >  Rx-pps:            0 >  Tx-pps:            0 >  ############################################################################ > >  ---------------------- Forward statistics for port 0 ---------------------- >  RX-packets: 1445160        RX-dropped: 0             RX-total: 1445160 >  TX-packets: 1602045        TX-dropped: 694971472     TX-total: 696573517 >  ---------------------------------------------------------------------------- > >  +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++ >  RX-packets: 1445160        RX-dropped: 0             RX-total: 1445160 >  TX-packets: 1602045        TX-dropped: 694971472     TX-total: 696573517 >  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > What could be the reason for such packet drop? What tuning of buffer/queue > size affects this ? > Those stats for TX-dropped just look wrong to me. Given that you received only 1.45 million packets, having dropped nearly 700 million doesn't make sense. Even the Tx packet counts - though more reasonable - are higher than the received count. In terms of testpmd settings, the rxq=1 and txq=1 settings are the default so aren't needed, and setting the number of forwarding cores to 2 shouldn't do anything as there is only a single receive queue which can't be shared among cores. Regards, /Bruce