DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vincent JARDIN <vincent.jardin@6wind.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: John Fastabend <john.fastabend@gmail.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Zhang, Helin" <helin.zhang@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] AVX2 Vectorized Rx/Tx functions for i40e
Date: Wed, 10 Jan 2018 15:25:23 +0100	[thread overview]
Message-ID: <cb6a0c2a-e305-a3e6-5bb5-c7e7e383f917@6wind.com> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B0722203E8@IRSMSX103.ger.corp.intel.com>

Le 10/01/2018 à 10:27, Richardson, Bruce a écrit :
>> Hi Bruce,
>>
>> Just curious, can you provide some hints on percent increase in at least
>> some representative cases? I'm just trying to get a sense of if this is
>> %5, 10%, 20%, more... I know mileage will vary depending on system, setup,
>> configuration, etc.
>>
> Best case conditions to test under are using testpmd as that is where any IO improvement will be most seen. As a ballpark figure though, on my system while testing testpmd with both 16B and 32B descriptors, (RX/TX ring sizes 1024/512) I saw ~15% performance increase, and sometimes quite a bit higher, e.g. when testing with 16B descriptors with larger burst sizes.

Hi Bruce,

Then, about the next limit after this performance increase: is it the 
board/Mpps capacity/PCI bus? If so, you should see that CPU usage on 
testpmd's cores to be decreased. Can you be more explicit about it?

What's about other packet size like 66 bytes? 122 bytes? which are not 
aligned on 64 bytes.

Thank you,
   Vincent

  reply	other threads:[~2018-01-10 14:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23 16:53 [dpdk-dev] [PATCH " Bruce Richardson
2017-11-23 16:53 ` [dpdk-dev] [PATCH 1/2] net/i40e: add AVX2 Tx function Bruce Richardson
2017-11-29  2:13   ` Ferruh Yigit
2017-11-29 10:02     ` Bruce Richardson
2017-11-23 16:53 ` [dpdk-dev] [PATCH 2/2] net/i40e: add AVX2 Rx function Bruce Richardson
2017-11-23 16:56 ` [dpdk-dev] [PATCH 0/2] AVX2 Vectorized Rx/Tx functions for i40e Bruce Richardson
2017-11-27 10:45 ` Zhang, Qi Z
2018-01-09 14:32 ` [dpdk-dev] [PATCH v2 " Bruce Richardson
2018-01-09 14:32   ` [dpdk-dev] [PATCH v2 1/2] net/i40e: add AVX2 Tx function Bruce Richardson
2018-01-09 14:32   ` [dpdk-dev] [PATCH v2 2/2] net/i40e: add AVX2 Rx function Bruce Richardson
2018-01-09 16:30   ` [dpdk-dev] [PATCH v2 0/2] AVX2 Vectorized Rx/Tx functions for i40e John Fastabend
2018-01-10  9:27     ` Richardson, Bruce
2018-01-10 14:25       ` Vincent JARDIN [this message]
2018-01-10 14:38         ` Bruce Richardson
2018-01-10  7:11   ` Li, Xiaoyun
2018-01-10  7:14   ` Zhang, Qi Z
2018-01-10 13:49     ` Zhang, Helin

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=cb6a0c2a-e305-a3e6-5bb5-c7e7e383f917@6wind.com \
    --to=vincent.jardin@6wind.com \
    --cc=beilei.xing@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=helin.zhang@intel.com \
    --cc=john.fastabend@gmail.com \
    --cc=qi.z.zhang@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).