From: Petr Mladek <pmladek@suse.com>
To: Bitao Hu <yaoma@linux.alibaba.com>
Cc: dianders@chromium.org, akpm@linux-foundation.org,
kernelfans@gmail.com, liusong@linux.alibaba.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv6 0/2] *** Detect interrupt storm in softlockup ***
Date: Fri, 9 Feb 2024 15:48:31 +0100 [thread overview]
Message-ID: <ZcY7P7KLDt90XqYE@alley> (raw)
In-Reply-To: <20240208125426.70511-1-yaoma@linux.alibaba.com>
On Thu 2024-02-08 20:54:24, Bitao Hu wrote:
> Hi, guys.
> I have implemented a low-overhead method for detecting interrupt
> storm in softlockup. Please review it, all comments are welcome.
I like this work.
I wonder if you might be interested also in reporting problems
when soft IRQs are offloaded to the "ksoftirqd/X" kthreads
for too long.
The kthreads are processes with normal priority. As a result,
offloading soft IRQs to kthreads might cause huge difference
on loaded systems.
I have seen several problems when a flood of softIRQs triggered
offloading them. And it caused several second delays on networking
interfaces.
Best Regards,
Petr
next prev parent reply other threads:[~2024-02-09 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 12:54 [PATCHv6 0/2] *** Detect interrupt storm in softlockup *** Bitao Hu
2024-02-08 12:54 ` [PATCHv6 1/2] watchdog/softlockup: low-overhead detection of interrupt Bitao Hu
2024-02-08 16:03 ` Doug Anderson
2024-02-09 13:35 ` Petr Mladek
2024-02-11 15:35 ` Bitao Hu
2024-02-11 23:46 ` Doug Anderson
2024-02-10 13:32 ` Liu Song
2024-02-08 12:54 ` [PATCHv6 2/2] watchdog/softlockup: report the most frequent interrupts Bitao Hu
2024-02-08 16:03 ` Doug Anderson
2024-02-11 15:41 ` Bitao Hu
2024-02-09 14:39 ` Petr Mladek
2024-02-11 15:36 ` Bitao Hu
2024-02-10 13:33 ` Liu Song
2024-02-09 14:48 ` Petr Mladek [this message]
2024-02-11 15:36 ` [PATCHv6 0/2] *** Detect interrupt storm in softlockup *** Bitao Hu
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=ZcY7P7KLDt90XqYE@alley \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=dianders@chromium.org \
--cc=kernelfans@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liusong@linux.alibaba.com \
--cc=yaoma@linux.alibaba.com \
/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).