From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 487] Worse performance with DPDK driver when MTU is set to 2022 or less
Date: Thu, 04 Jun 2020 14:17:50 +0000 [thread overview]
Message-ID: <bug-487-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=487
Bug ID: 487
Summary: Worse performance with DPDK driver when MTU is set to
2022 or less
Product: DPDK
Version: 20.02
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: vrpolak@cisco.com
Target Milestone: ---
This is a copy of issue VPP-1876 [0], opened against VPP project. See the
description and comments there (or let me know and I will copy them here).
Performance of VPP (NIC: Intel-xxv710) depends on MTU value set, but only when
DPDK driver is used. That does not prove the bug is in DPDK, but it is
suspicious enough for me to open this Bug against DPDK.
I tried to reproduce the behavior using other DPDK applications, but they tend
to hit the line rate regardless of MTU. Is there a DPDK application that
intentionally wastes some cycles, so I can try to confirm its performance
depends on MTU value?
[0] https://jira.fd.io/browse/VPP-1876
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-06-04 14:17 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-487-3@http.bugs.dpdk.org/ \
--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).