From: Steffen Weise <stweise.linux@gmail.com>
To: Filip Janiszewski <contact@filipjaniszewski.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] MLX ConnectX-4 Discarding packets
Date: Sat, 11 Sep 2021 12:20:00 +0200 [thread overview]
Message-ID: <ED97FC24-64D7-446B-9EE0-B818BBE30CAA@gmail.com> (raw)
In-Reply-To: <57ab0193-689d-55b9-6f8c-dc23682e7c06@filipjaniszewski.com>
Hi Filip,
i have not seen the same issues.
Are you aware of this tuning guide? I applied it and had no issues with intel 100G NIC.
HPC Tuning Guide for AMD EPYC Processors
http://developer.amd.com/wp-content/resources/56420.pdf
Hope it helps.
Cheers,
Steffen Weise
> Am 11.09.2021 um 10:56 schrieb Filip Janiszewski <contact@filipjaniszewski.com>:
>
> I ran more tests,
>
> This AMD server is a bit confusing, I can tune it to capture 28Mpps (64
> bytes frame) from one single core, so I would assume that using one more
> core will at least increase a bit the capture capabilities, but it's
> not, 1% more speed and it drops regardless of how many queues are
> configured - I've not observed this situation on the Intel server, where
> adding more queues/cores scale to higher throughput.
>
> This issue have been verified now with both Mellanox and Intel (810
> series, 100GbE) NICs.
>
> Anybody encountered anything similar?
>
> Thanks
>
> Il 9/10/21 3:34 PM, Filip Janiszewski ha scritto:
>> Hi,
>>
>> I've switched a 100Gbe MLX ConnectX-4 card from an Intel Xeon server to
>> an AMD EPYC server (running 75F3 CPU, 256GiB of RAM and PCIe4 lanes),
>> and using the same capture software we can't get any faster than 10Gbps,
>> when exceeding that speed regardless of the amount of queues configured
>> the rx_discards_phy counter starts to raise and packets are lost in huge
>> amounts.
>>
>> On the Xeon machine, I was able to get easily to 50Gbps with 4 queues.
>>
>> Is there any specific DPDK configuration that we might want to setup for
>> those AMD servers? The software is DPDK based so I wonder if some build
>> option is missing somewhere.
>>
>> What else I might want to look for to investigate this issue?
>>
>> Thanks
>>
>
> --
> BR, Filip
> +48 666 369 823
next prev parent reply other threads:[~2021-09-11 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 13:34 Filip Janiszewski
2021-09-11 8:56 ` Filip Janiszewski
2021-09-11 10:20 ` Steffen Weise [this message]
2021-09-11 14:19 ` Filip Janiszewski
2021-09-11 14:34 ` Filip Janiszewski
2021-09-12 9:32 ` Filip Janiszewski
2021-09-29 10:43 ` Thomas Monjalon
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=ED97FC24-64D7-446B-9EE0-B818BBE30CAA@gmail.com \
--to=stweise.linux@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).