DPDK usage discussions
 help / color / mirror / Atom feed
From: Filip Janiszewski <contact@filipjaniszewski.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] MLX ConnectX-4 Discarding packets
Date: Sat, 11 Sep 2021 10:56:26 +0200
Message-ID: <57ab0193-689d-55b9-6f8c-dc23682e7c06@filipjaniszewski.com> (raw)
In-Reply-To: <e3867350-42a9-e74e-7fd3-a239797514ac@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?


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

  reply	other threads:[~2021-09-11  8:56 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 [this message]
2021-09-11 10:20   ` Steffen Weise
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57ab0193-689d-55b9-6f8c-dc23682e7c06@filipjaniszewski.com \
    --to=contact@filipjaniszewski.com \
    --cc=users@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git