DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Vladyslav Buslov <Vladyslav.Buslov@harmonicinc.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
	"Pei, Yulong" <yulong.pei@intel.com>,
	"Zhang, Helin" <helin.zhang@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Nitin Kumar <Nitin.Kumar@harmonicinc.com>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: add packet prefetch
Date: Thu, 6 Apr 2017 10:54:54 +0100	[thread overview]
Message-ID: <20170406095454.GB3564@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <MWHPR11MB1360CE19E327290BD5AEAB009D0D0@MWHPR11MB1360.namprd11.prod.outlook.com>

On Thu, Apr 06, 2017 at 09:29:12AM +0000, Vladyslav Buslov wrote:
> Ferruh,
> 
> In our case patch significantly improves application performance. (~40% more PPS on load balancer core)
> Using DPDK examples I can only reproduce perf improvements with similar design apps like load_balancer.
> With applications that send on free packets on same core where they are received performance is not improved.
> 
> It seems that this patch doesn't do anything(or even actually slightly degrades performance) for run-to-completion apps so we will have to continue maintaining it as part part of our internal branch.
> 
> Regards,
> Vlad
>
Is it possible to get the same performance boost in your app, while
avoiding the perf hit in run-to-completion apps, by using a runtime,
rather than compile-time option?

/Bruce

  reply	other threads:[~2017-04-06  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 10:56 Vladyslav Buslov
2017-03-07 10:37 ` Ferruh Yigit
2017-04-01  2:01 ` Pei, Yulong
2017-04-03 10:31   ` Ferruh Yigit
2017-04-06  9:29     ` Vladyslav Buslov
2017-04-06  9:54       ` Bruce Richardson [this message]
2017-04-03 10:47   ` Ananyev, Konstantin
2017-04-06  9:54     ` Bruce Richardson

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=20170406095454.GB3564@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=Nitin.Kumar@harmonicinc.com \
    --cc=Vladyslav.Buslov@harmonicinc.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=helin.zhang@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=yulong.pei@intel.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).