From: Bruce Richardson <bruce.richardson@intel.com>
To: SwamZ <swamssrk@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Rx_missed_errors drops with larger packet size
Date: Fri, 20 May 2016 11:44:45 +0100 [thread overview]
Message-ID: <20160520104445.GB19260@bricha3-MOBL3> (raw)
In-Reply-To: <CAMh0sidbgTz=q90Q9jTbn7RVP5m8WqjSD1wyK+nT-w9iGAq3sA@mail.gmail.com>
On Fri, May 20, 2016 at 02:09:02AM -0700, SwamZ wrote:
> Hi,
>
>
> While doing performance testing with larger packet size (like 4000 bytes),
> we are seeing rx_missed_errors on the interface. This issue is not seen
> with packet size less than 2000. There were questions asked in this forum
> on rx_missed_error, but there was not any conclusion. Please let me know
> what could be the reason for these drops.
>
>
> I tried the following without any luck:
>
> 1) Tried different burst size like 16, 32 an 64
>
> 2) Tried different number of the rx descriptors like 512, 1024, 2048 and
> 4096.
>
>
> Setup and testing details:
>
> CPU Speed : 2.6 GHz
>
> NIC : 82599ES 10-Gigabit
>
> IO Virtualization: SR-IOV
>
> IO and packet processing cores are in the same NUMA.
>
> Packet size : 4000 bytes
>
> Traffic rate: 80 % line rate. If the traffic rate is < ~80% then drops are
> not seen.
>
> Application: This is a sample application developed using L3fwd example app.
>
> DPDK version: 1.7
Hi,
Couple of follow up questions:
1. Can you confirm that you are using the standard ~2k buffer size, implying
that you are using the slower scattered RX/TX code paths for the 4k packet size
case? If so, can you try increasing your buffer size to 5k and see what happens?
2. Does the issue still occur on the latest DPDK 16.04 release, or on the latest
code on dpdk.org. Release 1.7 is very old at this stage.
Regards,
/Bruce
next prev parent reply other threads:[~2016-05-20 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 9:09 SwamZ
2016-05-20 10:44 ` Bruce Richardson [this message]
2016-05-20 16:45 ` Alexander Duyck
2016-05-20 21:47 ` SwamZ
2016-05-31 18:50 ` SwamZ
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=20160520104445.GB19260@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=swamssrk@gmail.com \
/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).