From: Antoine POLLENUS <a.pollenus@deltacast.tv>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Understand main Lcore
Date: Mon, 14 Feb 2022 08:49:09 +0000 [thread overview]
Message-ID: <50abd2e008604ec08ce7850281adf1c0@deltacast.tv> (raw)
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
Hello,
We are struggling to understand how the main lcore works and what is exactly done in it when it run.
This need of understanding come from some issues we see when setting the main lcore on the core 0 NUMA 0.
When we do that we see some latency spike in the packet interval time like if the tx_burst was blocked for 1ms despite being on another lcore than the main one.
The spike are really annoying because our usecase is time sensitive.
The questions are:
- What is the exact role of the main lcore?
- How does the main lcore works ?
- Do you have recommendation on which cpu core to assign main lcore ?
- Why would we observe the packet interval time only on core 0 ?
- Is there an implication of having interrupt on the main lcore on the other lcore ?
Thank you in advance for your help,
Antoine
[-- Attachment #2: Type: text/html, Size: 9499 bytes --]
next reply other threads:[~2022-02-14 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 8:49 Antoine POLLENUS [this message]
2022-02-14 16:47 ` Stephen Hemminger
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=50abd2e008604ec08ce7850281adf1c0@deltacast.tv \
--to=a.pollenus@deltacast.tv \
--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).