<div dir="auto">Also make sure all core you are using are physical core not the logical core. </div><div dir="auto">Secondly, check your core isolation options and apply them accordingly.</div><div dir="auto"><br clear="all"><br clear="all"><div dir="auto"><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><font face="georgia, serif" style="font-family:georgia,serif;color:rgb(53,28,117)">.</font><div><font face="georgia, serif" style="font-family:georgia,serif;color:rgb(53,28,117)"><br></font></div><div><font face="georgia, serif" style="font-family:georgia,serif;color:rgb(53,28,117)">Regards,</font></div><div><font face="georgia, serif" style="font-family:georgia,serif;color:rgb(53,28,117)">Nishant Verma</font></div></div></div></div></div><div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 23, 2024 at 6:04 PM Wisam Jaddo <<a href="mailto:wisamm@nvidia.com">wisamm@nvidia.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">Hello Amit,<br>
<br>
> -----Original Message-----<br>
> From: amit sehas <<a href="mailto:cun23@yahoo.com" target="_blank">cun23@yahoo.com</a>><br>
> Sent: Monday, September 23, 2024 11:57 PM<br>
> To: <a href="mailto:users@dpdk.org" target="_blank">users@dpdk.org</a><br>
> Subject: core performance<br>
> <br>
> We are seeing different dpdk threads (launched via rte_eal_remote_launch()),<br>
> demonstrate very different performance.<br>
> <br>
> <br>
> <br>
> After placing counters all over the code, we realize that some threads are<br>
> uniformly slow, in other words there is no application level issue that is<br>
> throttling one thread over the other. We come to the conculsion that either<br>
> the Cores on which they are running are not at the same frequency which<br>
> seems doubtful or the threads are not getting a chance to execute on the cores<br>
> uniformly.<br>
> <br>
> <br>
> <br>
> It seems that isolcpus has been deprecated in recent versions of linux.<br>
> <br>
> <br>
> <br>
> What is the recommended approach to prevent the kernel from utilizing some<br>
> CPU threads, for anything other than the threads that are launched on them.<br>
<br>
If you are wishing to run each thread on separate core, try to use rte_eal_mp_remote_launch()<br>
instead of rte_eal_remote_launch(), make sure that your CPU is isolated, and you are passing correct<br>
Cores that were isolated to your app using -c, -l.<br>
<br>
<br>
> <br>
> <br>
> <br>
> Is there some API in dpdk which also helps us determine which CPU core the<br>
> thread is pinned to?<br>
> <br>
> I did not find any code in dpdk which actually performed pinning of a thread to<br>
> a CPU core.<br>
> <br>
> <br>
> <br>
> In our case it is more or less certain that the different threads are simply not<br>
> getting the same CPU core time, as a result some are demonstrating higher<br>
> throughput than the others ...<br>
> <br>
> <br>
> <br>
> how do we fix this?<br>
<br>
BRs,<br>
Wisam Jaddo<br>
</blockquote></div></div>