On Mon, 14 Feb 2022 08:49:09 +0000 Antoine POLLENUS <a.polle...@deltacast.tv> wrote:
> 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? Nothing special by default. It is the initial thread created when DPDK program is started. It is bound to first CPU during rte_eal_init() > - How does the main lcore works ? It is just a pthread. If you need to know the internals (which you should if you are debugging this kind of thing); then read eal.c > - Do you have recommendation on which cpu core to assign main lcore ? Same as all the others. Core selection in general is related to NUMA and CPU topology. Use the DPDK cpu-layout script to see what your environment looks like. > - Why would we observe the packet interval time only on core 0 ? Linux kernel uses core 0 for timer ticks and other housekeeping, don't use it for packet processing. Did you isolate the DPDK application from other processes in the system. > - Is there an implication of having interrupt on the main lcore on the other > lcore ? Interrupts take higher priority than normal user processes. And they must run or the system will starve. > Thank you in advance for your help, > > Antoine
