DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gudimetla, Leela Sankar" <lgudimet@ciena.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "hhaim@cisco.com" <hhaim@cisco.com>
Subject: Re: [dpdk-dev] DPDK 17.02 RC-3 performance degradation of ~10%
Date: Wed, 21 Jun 2017 21:24:02 +0000	[thread overview]
Message-ID: <CY4PR04MB0520C34B079BC552F19DFDB1DADA0@CY4PR04MB0520.namprd04.prod.outlook.com> (raw)

Hi,

"Existing thread subject: DPDK 17.02 RC-3 performance degradation of ~10%"

We are in the process of upgrading from dpdk 16.11 to 17.02. We are also seeing performance degradation in our packet processing application for about ~3% with 17.02.
When we browsed through mailing lists, we found a similar thread as mentioned in this email subject from Cisco T-Rex. But the thread did not point to any resolution instead they could fix it in their software.
Before starting to figure out which commit of dpdk (git bisect) is causing our application to degrade (which is tedious and slow), we are wondering that if the resolution for the T-Rex is shared in broad sense like which dpdk api etc.
That would really help.

Thanks & Regards,
Leela sankar Gudimetla

             reply	other threads:[~2017-06-21 21:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 21:24 Gudimetla, Leela Sankar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-06-21 22:06 Gudimetla, Leela Sankar
2017-02-14 11:44 Hanoch Haim (hhaim)
2017-02-14 12:19 ` Mcnamara, John
2017-02-14 12:31   ` Hanoch Haim (hhaim)
2017-02-14 13:04   ` Thomas Monjalon
2017-02-14 13:28     ` De Lara Guarch, Pablo
2017-02-14 13:38       ` De Lara Guarch, Pablo
2017-02-15 12:35     ` Hanoch Haim (hhaim)

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=CY4PR04MB0520C34B079BC552F19DFDB1DADA0@CY4PR04MB0520.namprd04.prod.outlook.com \
    --to=lgudimet@ciena.com \
    --cc=dev@dpdk.org \
    --cc=hhaim@cisco.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).