From: Lokesh Chakka <lvenkatakumarchakka@gmail.com>
To: Filip Janiszewski <contact@filipjaniszewski.com>
Cc: users <users@dpdk.org>
Subject: Re: DPDK 22.03 substantially slower with Intel E810-C
Date: Thu, 4 Aug 2022 16:23:06 +0530 [thread overview]
Message-ID: <CACh--sjiybmtZTgM7KSo5DDiyd_nfkUYjSuiDVWUHKdvfdRfJw@mail.gmail.com> (raw)
In-Reply-To: <9c1d187e-d2b5-686b-d337-16081715ef7a@filipjaniszewski.com>
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
You are lucky. At least it is working. The E810-2CQDA2 Intel card I have
purchased is shutting down immediately after devbind. Even the technical
support is pathetic. It is one week I raised the issue and no progressive
response till now.
--
Lokesh
On Thu, Aug 4, 2022, 15:52 Filip Janiszewski <contact@filipjaniszewski.com>
wrote:
> 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
>
[-- Attachment #2: Type: text/html, Size: 1576 bytes --]
prev parent reply other threads:[~2022-08-04 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 10:22 Filip Janiszewski
2022-08-04 10:53 ` Lokesh Chakka [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=CACh--sjiybmtZTgM7KSo5DDiyd_nfkUYjSuiDVWUHKdvfdRfJw@mail.gmail.com \
--to=lvenkatakumarchakka@gmail.com \
--cc=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).