From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Li, Xiaoyun" <xiaoyun.li@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v3] app/testpmd: fix little perf drop
Date: Wed, 18 Jul 2018 11:10:51 +0100 [thread overview]
Message-ID: <6696fbcb-d8a7-0fac-9c7d-e0c5b9c8fdf5@intel.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09093B804DF9@shsmsx102.ccr.corp.intel.com>
On 7/16/2018 4:02 AM, Lu, Wenzhuo wrote:
> Hi,
>
>> -----Original Message-----
>> From: Li, Xiaoyun
>> Sent: Thursday, July 12, 2018 3:56 PM
>> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Lu, Wenzhuo
>> <wenzhuo.lu@intel.com>
>> Cc: dev@dpdk.org; Li, Xiaoyun <xiaoyun.li@intel.com>; stable@dpdk.org
>> Subject: [PATCH v3] app/testpmd: fix little perf drop
>>
>> There is about 3% perf drop. And it is because of a bitrate calculation in the
>> datapath. So improve it by maintaining an array of port indexes in testpmd,
>> which is updated with ethdev events.
>>
>> Fixes: 8728ccf37615 ("fix ethdev ports enumeration")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com>
> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
Applied to dpdk-next-net/master, thanks.
Is it possible that someone from test team confirm that performance recovered
after this commit and report to mail list?
Thanks,
ferruh
prev parent reply other threads:[~2018-07-18 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 2:28 [dpdk-dev] [PATCH] app/testpmd: fix little perf drop with XL710 Xiaoyun Li
2018-07-10 4:31 ` Zhang, Qi Z
2018-07-11 2:15 ` [dpdk-dev] [PATCH v2] " Xiaoyun Li
2018-07-12 4:56 ` Zhang, Qi Z
2018-07-12 5:56 ` Lu, Wenzhuo
2018-07-12 8:01 ` Li, Xiaoyun
2018-07-12 7:55 ` [dpdk-dev] [PATCH v3] app/testpmd: fix little perf drop Xiaoyun Li
2018-07-16 3:02 ` Lu, Wenzhuo
2018-07-18 10:10 ` Ferruh Yigit [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=6696fbcb-d8a7-0fac-9c7d-e0c5b9c8fdf5@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.com \
--cc=xiaoyun.li@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).