DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kuusisaari, Juhamatti" <Juhamatti.Kuusisaari@coriant.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK 1705 on libpcap drivers has drops?
Date: Tue, 3 Oct 2017 05:33:07 +0000	[thread overview]
Message-ID: <AM6PR0402MB3398844631A7868AA436ECB89D720@AM6PR0402MB3398.eurprd04.prod.outlook.com> (raw)


Hello,

We are testing on 1705 over libpcap driver and unfortunately we are seeing surprisingly large drops. They are seen with low rate/ping randomly and with high rate the throughput is very limited (even 30 % drops seen) compared to our reference system on DPDK 1.7.1. The only thing changed in the system is the DPDK version and its internals. 

I'll look into the problem next, but any hints where to look first? What changes between 1.7.1 and 1705 could perhaps cause such behavíour?

Thanks,
--
 Juhamatti
 

             reply	other threads:[~2017-10-03  5:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03  5:33 Kuusisaari, Juhamatti [this message]
2017-10-19  8:03 Kuusisaari, Juhamatti
2017-10-19 16:22 ` Ferruh Yigit

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=AM6PR0402MB3398844631A7868AA436ECB89D720@AM6PR0402MB3398.eurprd04.prod.outlook.com \
    --to=juhamatti.kuusisaari@coriant.com \
    --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).