From: "Nicolson Ken (ニコルソン ケン)" <ken.nicolson@jp.panasonic.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Downstream PMD running on same core, leading to horrible performance
Date: Thu, 2 Nov 2023 08:12:50 +0000 [thread overview]
Message-ID: <TYCPR01MB11476174113D9FE6ADBDF3238BCA6A@TYCPR01MB11476.jpnprd01.prod.outlook.com> (raw)
Hi everyone,
I've got a stand-alone executable that auto-loads PMDs with the usual rte_eal_init() call, but the performance is horrible at higher speeds, and it looks like my call to rte_eth_tx_burst() is being handled by a different thread, but running in the same core, so I end up losing lots of packets as the downstream rx buffer fills up quicker than it can be emptied.
rte_lcore_count() reports just one core, so is there some way to get either my main code or the downstream PMD (vhost, by the way) to run on a separate core.
I'm sending iperf3-generated TCP traffic wrapped as ROS2 messages, so I have just got simple code that copies the message bytes from ROS2 format to mbufs, but at about 10 Gbps and 1400 byte packets I'm losing about 10000 packets per second through rte_eth_tx_burst() errors! If I comment out that function call, the code can keep up, so I don't believe it is my upstream code.
Any hints on how to fix this would be helpful.
Thanks,
Ken
reply other threads:[~2023-11-02 8:12 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=TYCPR01MB11476174113D9FE6ADBDF3238BCA6A@TYCPR01MB11476.jpnprd01.prod.outlook.com \
--to=ken.nicolson@jp.panasonic.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).