From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 33347A0353 for ; Tue, 1 Mar 2022 16:31:26 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 030B2426DE; Tue, 1 Mar 2022 16:31:26 +0100 (CET) Received: from mail-ed1-f43.google.com (mail-ed1-f43.google.com [209.85.208.43]) by mails.dpdk.org (Postfix) with ESMTP id 7BD5F40DF6 for ; Tue, 1 Mar 2022 16:31:24 +0100 (CET) Received: by mail-ed1-f43.google.com with SMTP id q17so22490241edd.4 for ; Tue, 01 Mar 2022 07:31:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1CR8fzUnI7X7Kafaf034Ior1ib00b57kYrJ6qvdEHsU=; b=lBhRzfzuwRHtjGZZUMdW70UKm9B/fWPsfrpsswqMQc6T1xtemlU2iHr0Ks1J3ZP5CC OP4PJkygp1xKr8bqxgtWctoFt3zqYiztucBbpkgVWT/QIqxpB8IgijNkh5tLY2z45p0f cq3So1iK6MkJYL+hh+iQ8lhuKrmtVBBY4iFFiAICpGFT3voxC0y/bQ67UoRueG3sjxwl jVlegMKcOP6dtK8wSYliaCYFW2aNfmSNU/0cUemqPnxdwsmnqgg57lV0l10mm4N6ryIV CayAXDUVXxkCwNSdmLTnxifoNj7ejQ6LvUXTfQF7rfjfN7V6Rn9XYcbngg7OhqtUGEvK Znng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1CR8fzUnI7X7Kafaf034Ior1ib00b57kYrJ6qvdEHsU=; b=MricIY/gNV7Is6dLNRUBeEBBl2tzXe9QWWwPoC9wdpTWvjsFHq+Tx4t9e+jn+9kprR 53TJfBaBe5yo1nlVCJJaECt0xOZNwiwVufzsTMTXFUIYtH0uQLKmRVwxIZQcxakH/4y0 eNizAlmeCXD8LTDHvPdMQA9emO/rIXeF+mlVUUuPz7zAMQESlRJlGPsHWZz3RTCJHEZS RKuo2HUWBkhGAQ+eb4XZ/FdnOoCTAvqX6X1OdVHM6yI2OOSj8nTaf+mSiE6OtHbg+V5L Mc7zORY7uq0ul5l6W7C9rlwKRLkEf2H7DLN1qlw3od/1XJwEKkoZ5yXBKsPqvQ4w9I1t h7wQ== X-Gm-Message-State: AOAM530BKjS8NIbEbAARWLSPofBK34j91RD7bS9u7ChEybs6PdIViobP 2JstrQUkVEVYIaUvkmY8y3asdhohrIJx7vVBfo5u2vm1 X-Google-Smtp-Source: ABdhPJwuR18ndLhmu2XKsfHZ3/BYt9h0Zm4gJy2WJUe+KegsasgaJtzj5dyEHsqb0d49kgXRHwyONCjVqB+jPCn+QwM= X-Received: by 2002:a05:6402:528e:b0:407:80ff:6eed with SMTP id en14-20020a056402528e00b0040780ff6eedmr24989106edb.165.1646148683940; Tue, 01 Mar 2022 07:31:23 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Cliff Burdick Date: Tue, 1 Mar 2022 07:31:11 -0800 Message-ID: Subject: Re: DPDK on isolated cores but I still see interrupts To: Antonio Di Bacco Cc: users Content-Type: multipart/alternative; boundary="0000000000008dc5cf05d929dbb0" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --0000000000008dc5cf05d929dbb0 Content-Type: text/plain; charset="UTF-8" One thing you can try is using the irqaffinity boot parameter to force interrupts onto your non-isolated cores: For timer interrupts you can try running in NO_HZ_FULL mode, but that may not work if you have other userspace processes running on those cores. It might be worth confirming that the interrupts are actually causing noticeable problems first before trying to move the interrupts. On Tue, Mar 1, 2022 at 6:52 AM Antonio Di Bacco wrote: > I am trying to run a DPDK application on x86_64 Machine (Ubuntu 20.04) on > isolated cores. > I expected not to have interrupts on isolated cores but I still have a lot > of CAL (*Function call interrupts*) interrupts and LOC interrupts (*Local > timer interrupts*). Is there any setting in DPDK to stop those too? > > Regards. > --0000000000008dc5cf05d929dbb0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
One thing you can try is using the irqaffinity boot parame= ter to force interrupts onto your non-isolated cores: For timer interrupts = you can try running in NO_HZ_FULL mode, but that may not work if you have o= ther userspace processes running on those cores. It might be worth confirmi= ng that the interrupts are actually causing noticeable problems first befor= e trying to move the interrupts.

On Tue, Mar 1, 2022 at 6:52 AM Antonio Di B= acco <a.dibacco.ks@gmail.com> wrote:
I am trying to run a DPDK application on x86_64 Machine (Ubu= ntu 20.04) on isolated cores.
I expected not to have interru= pts on isolated cores but I still have a lot of CAL (Function call inter= rupts) interrupts and LOC interrupts (Local timer interrupts<= /b>). Is there any setting in DPDK to stop those too?

=
Regards.
--0000000000008dc5cf05d929dbb0--