From: Vincent JARDIN <vincent.jardin@6wind.com>
To: "Wang, Qihua (NSB - CN/Hangzhou)" <qihua.wang@nokia-sbell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] avp pmd driver performance decreased from DPDK 1604 to 1705
Date: Wed, 23 May 2018 08:59:25 +0200 [thread overview]
Message-ID: <d12cc4e8-3efc-8877-da84-130726a8eb77@6wind.com> (raw)
In-Reply-To: <DB6PR07MB3255B17BB15A16CD9825F2C8DB6B0@DB6PR07MB3255.eurprd07.prod.outlook.com>
Le 23/05/2018 à 07:52, Wang, Qihua (NSB - CN/Hangzhou) a écrit :
> Hi DPDK expert,
> I am Nokia engineer. We are upgrading 6wind from 6wind 4.13->4.17, with DPDK upgrading from 16.04->17.05. We use AVP PMD driver.
> From the performance test result, the CPU load of RX core increase from 72% to 94% under same pps. The bitrate decreased from 9800M to 9000M, limitation is also in RX core.
> The difference is only 6wind software and DPDK code.
> Do you have some test result for DPDK AVP PMD driver for release 16.04 and 17.05?
> Do you have some suggestion to increase the AVP PMD driver performance? Is the later version have any improvement for AVP?
>
> Waiting for your response.
For such issues, I strongly advise that you contact your 6WIND's support
person. People on this mailing list may not care about performance
degradation with WindRiver's AVP PMD.
My advise regarding PMD performances: you should check with testpmd +
AVP PMD if there is any performance decrease. testpmd is used to isolate
and test specifically the throughput of the drivers.
When you'll run testpmd, you can check any differences using "perf top"
with both versions of DPDK and then you should report these differences
to some DPDK experts.
best regards,
Vincent
prev parent reply other threads:[~2018-05-23 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DB6PR07MB3255482FB6A3241A5E6C7C33DB940@DB6PR07MB3255.eurprd07.prod.outlook.com>
2018-05-23 5:52 ` Wang, Qihua (NSB - CN/Hangzhou)
2018-05-23 6:59 ` Vincent JARDIN [this message]
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=d12cc4e8-3efc-8877-da84-130726a8eb77@6wind.com \
--to=vincent.jardin@6wind.com \
--cc=dev@dpdk.org \
--cc=qihua.wang@nokia-sbell.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).