DPDK usage discussions
 help / color / mirror / Atom feed
From: Cliff Burdick <shaklee3@gmail.com>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: DPDK on isolated cores but I still see interrupts
Date: Tue, 1 Mar 2022 07:31:11 -0800	[thread overview]
Message-ID: <CA+Gp1nY0r5drA9UX9mNoEDjW54Pt+JARV_gw7Ft-i_HqPSPiZQ@mail.gmail.com> (raw)
In-Reply-To: <CAO8pfFnr43DYs7ianmPKU_=Q5uRfC91ReXF-+zT+GmKrwJbn8Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 805 bytes --]

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 <a.dibacco.ks@gmail.com>
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.
>

[-- Attachment #2: Type: text/html, Size: 1546 bytes --]

      parent reply	other threads:[~2022-03-01 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 14:52 Antonio Di Bacco
2022-03-01 15:16 ` Kinsella, Ray
2022-03-01 16:37   ` Stephen Hemminger
2022-03-01 15:31 ` Cliff Burdick [this message]

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=CA+Gp1nY0r5drA9UX9mNoEDjW54Pt+JARV_gw7Ft-i_HqPSPiZQ@mail.gmail.com \
    --to=shaklee3@gmail.com \
    --cc=a.dibacco.ks@gmail.com \
    --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).