From: "Nicolson Ken (ニコルソン ケン)" <ken.nicolson@jp.panasonic.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: RE: Removing user threads from DPDK management
Date: Thu, 30 Nov 2023 06:56:35 +0000 [thread overview]
Message-ID: <OSZPR01MB774844687E762FFFBA4BA533BC82A@OSZPR01MB7748.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <OSZPR01MB7748041678B6121D85AABD1BBC82A@OSZPR01MB7748.jpnprd01.prod.outlook.com>
Please ignore this thread - my calling of rte_eal_init() forgot that argv[0] should be the program name, so instead I had argv[0]="--lcores=....".
Thanks,
Ken
-----Original Message-----
From: Nicolson Ken (ニコルソン ケン) <ken.nicolson@jp.panasonic.com>
Sent: Thursday, November 30, 2023 12:27 PM
To: users@dpdk.org
Subject: RE: Removing user threads from DPDK management
PS: I should have added my debug info:
EAL: lib.eal log level changed from info to debug
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 0 on socket 0
EAL: Detected lcore 2 as core 4 on socket 0
EAL: Detected lcore 3 as core 4 on socket 0
EAL: Detected lcore 4 as core 8 on socket 0
EAL: Detected lcore 5 as core 8 on socket 0
EAL: Detected lcore 6 as core 12 on socket 0
EAL: Detected lcore 7 as core 12 on socket 0
EAL: Detected lcore 8 as core 16 on socket 0
EAL: Detected lcore 9 as core 16 on socket 0
EAL: Detected lcore 10 as core 20 on socket 0
EAL: Detected lcore 11 as core 20 on socket 0
EAL: Detected lcore 12 as core 24 on socket 0
EAL: Detected lcore 13 as core 24 on socket 0
EAL: Detected lcore 14 as core 28 on socket 0
EAL: Detected lcore 15 as core 28 on socket 0
EAL: Detected lcore 16 as core 36 on socket 0
EAL: Detected lcore 17 as core 37 on socket 0
EAL: Detected lcore 18 as core 38 on socket 0
EAL: Detected lcore 19 as core 39 on socket 0
EAL: Maximum logical cores by configuration: 128
EAL: Detected CPU lcores: 20
...
EAL: Main lcore 0 is ready (tid=7f345510b680;cpuset=[0])
EAL: lcore 1 is ready (tid=7f3440c08640;cpuset=[1])
EAL: lcore 2 is ready (tid=7f3423fff640;cpuset=[2])
EAL: lcore 4 is ready (tid=7f3422ffd640;cpuset=[4])
EAL: lcore 5 is ready (tid=7f34227fc640;cpuset=[5])
EAL: lcore 3 is ready (tid=7f34237fe640;cpuset=[3])
EAL: lcore 7 is ready (tid=7f34217fa640;cpuset=[7])
EAL: lcore 6 is ready (tid=7f3421ffb640;cpuset=[6])
EAL: lcore 9 is ready (tid=7f3407fff640;cpuset=[9])
EAL: lcore 10 is ready (tid=7f34077fe640;cpuset=[10])
EAL: lcore 11 is ready (tid=7f3406ffd640;cpuset=[11])
EAL: lcore 13 is ready (tid=7f3405ffb640;cpuset=[13])
EAL: lcore 12 is ready (tid=7f34067fc640;cpuset=[12])
EAL: lcore 8 is ready (tid=7f3420ff9640;cpuset=[8])
EAL: lcore 14 is ready (tid=7f34057fa640;cpuset=[14])
EAL: lcore 15 is ready (tid=7f3404ff9640;cpuset=[15])
EAL: lcore 18 is ready (tid=7f33f6ffd640;cpuset=[18])
EAL: lcore 16 is ready (tid=7f33f7fff640;cpuset=[16])
EAL: lcore 17 is ready (tid=7f33f77fe640;cpuset=[17])
EAL: lcore 19 is ready (tid=7f33f67fc640;cpuset=[19])
This is with --lcores='4@(12,16)' , but I'm not seeing any grouping going on.
Thanks,
Ken
-----Original Message-----
From: Nicolson Ken (ニコルソン ケン) <ken.nicolson@jp.panasonic.com>
Sent: Thursday, November 30, 2023 12:15 PM
To: users@dpdk.org
Subject: Removing user threads from DPDK management
Hi all,
I have an application framework that starts up two shared libraries in two separate threads. One of these libraries is mine, and in its initialisation I call rte_eal_init(). However, this has the unfortunate side-effect of making both threads run on the same CPU core, resulting in a throughput drop from an ideal 2.5Gbps to about 1Gbps. I've tried options like:
--lcores='(0-19)@(0-19)'
Or
taskset f start_framework other_lib.so my_dpdk_lib.so then in my_dpdk_lib.so code:
rte_eal_init(2, {"-c", "fff0"});
Or in my_dpdk_lib.so code
rte_thread_unregister();
And various combinations of the above, but nothing works.
I've read the Programmer's Guide chapter 4.3, but I'm not getting anything to work. Am I missing something simple, or is there anywhere I can get a more in-depth explanation of this stuff?
Thanks,
Ken
prev parent reply other threads:[~2023-11-30 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 3:15 Nicolson Ken (ニコルソン ケン)
2023-11-30 3:27 ` Nicolson Ken (ニコルソン ケン)
2023-11-30 6:56 ` Nicolson Ken (ニコルソン ケン) [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=OSZPR01MB774844687E762FFFBA4BA533BC82A@OSZPR01MB7748.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).