From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 48] Unexpected performance regression since CVE-2018-1059 fix with vector path
Date: Fri, 18 May 2018 16:01:41 +0000 [thread overview]
Message-ID: <bug-48-3@http.dpdk.org/tracker/> (raw)
https://dpdk.org/tracker/show_bug.cgi?id=48
Bug ID: 48
Summary: Unexpected performance regression since CVE-2018-1059
fix with vector path
Product: DPDK
Version: 18.05
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: vhost/virtio
Assignee: dev@dpdk.org
Reporter: maxime.coquelin@redhat.com
Target Milestone: ---
A small performance drop was expected with CVE-2018-1059 fix integration.
While this expectation is verified for mast cases (less than 3% drop), a bigger
drop is seen when using vector path in guest with small packets.
The goal of this ticket is to see if this performance regression can be
improved.
For reference, below is a copy paste from Lei Yao mail reporting the issue:
During the 18.05-rc1 performance testing, I find this patch set will bring
slightly performance drop on mergeable and normal path, and big performance
drop on vector path. Could you have a check on this? I know this patch is
important for security. Not sure if there is any way to improve the
performance.
Mergebale
packet size
64 0.80%
128 -2.75%
260 -2.93%
520 -2.72%
1024 -1.18%
1500 -0.65%
Normal
packet size
64 -1.47%
128 -7.43%
260 -3.66%
520 -2.52%
1024 -1.19%
1500 -0.78%
Vector
packet size
64 -8.60%
128 -3.54%
260 -2.63%
520 -6.12%
1024 -1.05%
1500 -1.20%
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
OS: Ubuntu 16.04
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-05-18 16:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-48-3@http.dpdk.org/tracker/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).