DPDK usage discussions
 help / color / mirror / Atom feed
From: Filip Janiszewski <contact@filipjaniszewski.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: DPDK 22.03 substantially slower with Intel E810-C
Date: Thu, 4 Aug 2022 12:22:41 +0200	[thread overview]
Message-ID: <9c1d187e-d2b5-686b-d337-16081715ef7a@filipjaniszewski.com> (raw)

Hello,

DPDK 22.03 contains quite some changed to the ICE driver and the
implementation for the Intel E810-C card, I'm running some tests and
while switching to this new version from 21.02 I see a degradation of
performance of around 30% using 4 capture core with 40Gbps rate (64bytes
frame), packets are random and evenly distributed among the cores.

Leaving unchanged all the other factors and only updating the library I
start observing substantial packet drops, using igb_uio and firmware
version 3.00 0x80008256 1.2992.0, I do not see any drop with 21.02.

Is there any novel configuration to be made during initialization of the
card or something like that? Anyone else is observing performance drop
with the new dpdk?

Thanks

-- 
BR, Filip
+48 666 369 823

             reply	other threads:[~2022-08-04 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 10:22 Filip Janiszewski [this message]
2022-08-04 10:53 ` Lokesh Chakka

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=9c1d187e-d2b5-686b-d337-16081715ef7a@filipjaniszewski.com \
    --to=contact@filipjaniszewski.com \
    --cc=users@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).