From: Bruce Richardson <bruce.richardson@intel.com>
To: Nilesh <nileshunhale@cse.iitb.ac.in>
Cc: dev@dpdk.org, users@dpdk.org
Subject: Re: [dpdk-dev] TX-dropped is high while sending custom packet via testpmd app
Date: Tue, 16 Jul 2019 10:43:41 +0100 [thread overview]
Message-ID: <20190716094341.GA572@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <a61f6c41-05db-0936-bf6c-90313bb18be5@cse.iitb.ac.in>
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
prev parent reply other threads:[~2019-07-16 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 9:31 Nilesh
2019-07-16 9:43 ` Bruce Richardson [this message]
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=20190716094341.GA572@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nileshunhale@cse.iitb.ac.in \
--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).