From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <users-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id A9F42A0093
	for <public@inbox.dpdk.org>; Thu, 23 Jun 2022 20:07:51 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 3A6864067B;
	Thu, 23 Jun 2022 20:07:51 +0200 (CEST)
Received: from guvercin.ceng.metu.edu.tr (guvercin.ceng.metu.edu.tr
 [144.122.171.43])
 by mails.dpdk.org (Postfix) with ESMTP id 394EA40146
 for <users@dpdk.org>; Thu, 23 Jun 2022 20:07:50 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by guvercin.ceng.metu.edu.tr (Postfix) with ESMTP id A334F2CBBA;
 Thu, 23 Jun 2022 21:07:49 +0300 (+03)
X-Virus-Scanned: Debian amavisd-new at ceng.metu.edu.tr
Received: from guvercin.ceng.metu.edu.tr ([127.0.0.1])
 by localhost (guvercin.ceng.metu.edu.tr [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id r-EQXdqoNsOL; Thu, 23 Jun 2022 21:07:40 +0300 (+03)
Received: from roundcube.ceng.metu.edu.tr (kanarya.ceng.metu.edu.tr
 [144.122.171.33])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested) (Authenticated sender: e1885458)
 by guvercin.ceng.metu.edu.tr (Postfix) with ESMTPSA id D8CC42C214;
 Thu, 23 Jun 2022 21:07:39 +0300 (+03)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ceng.metu.edu.tr;
 s=mail; t=1656007660;
 bh=m9Smv9eqQB2n9qiltBQ411b73uKL9ZiRu31iiaC21Rg=;
 h=Date:From:To:Cc:Subject:In-Reply-To:References:From;
 b=Wg4EycjH1C6W3DW9flxVVW8IYRTmez6EjAYYAsEovBdd39/WdP8Ie9Uhzva80iiI5
 JOaZU5WlWQADvtS6MMtqFEkGVWyXSZnOKKrJBdIPIfOEPWu+U9yVXTIRSr6crI/Mfk
 RWI24Hs0AfY3YS1fiwzRrrwYc2NI3pnzAfHckg/0=
MIME-Version: 1.0
Date: Thu, 23 Jun 2022 21:07:39 +0300
From: Omer Yamac <omer.yamac@ceng.metu.edu.tr>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: Large interruptions for EAL thread running on isol core
In-Reply-To: <CAO8pfF=yo37Ng5QAcopL=6LgKMHr4+=pPcONPATyS+OD0GLgfg@mail.gmail.com>
References: <CAO8pfF=yo37Ng5QAcopL=6LgKMHr4+=pPcONPATyS+OD0GLgfg@mail.gmail.com>
User-Agent: Roundcube Webmail
Message-ID: <f0aedbfa50c2c07616c6032e501171e6@ceng.metu.edu.tr>
X-Sender: omer.yamac@ceng.metu.edu.tr
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
Errors-To: users-bounces@dpdk.org

Hi Antonio,

Did you try to disable logical cores on CPU?

On 23.06.2022 21:03, Antonio Di Bacco wrote:
> I'm running a DPDK thread on an isolated core. I also set some  flags
> that could help keeping the core at rest on linux like: nosoftlockup
> nohz_full rcu_nocbs irqaffinity.
> 
> Unfortunately the thread gets some interruptions that stop the thread
> for about 20-30 micro seconds. This seems smal but my application
> suffers a lot.
> 
> I also tried to use  rte_thread_set_priority that indeed has a strong
> effect but unfortunately creates problems to Linux (like network not
> working).
> 
> Is there any other knob that could help running the DPDK thread with
> minimum or no interruptions at all?