From: Nicholas Piggin <npiggin@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH] kernel/irq/proc: /proc/interrupts irq-off latency reduction
Date: Thu, 5 Apr 2018 21:53:13 +1000 [thread overview]
Message-ID: <20180405115313.29821-1-npiggin@gmail.com> (raw)
Reading /proc/interrupts shows up as a latency source of several
hundred microseconds on a 2 socket 176 thread system, because it
iterates twice over all CPUs under an irq lock pulling in remote
cachelines, doing lots of seq_printf, etc.
On a 16 socket system with higher latencies to remote cachelines,
latencies around 10ms would be seen here. irqbalanced periodically
reads this file, and the latency spikes are noticed on smaller
systems. Also the file is unprivileged, so it's important to reduce
this latency.
Avoid holding the lock while iterating over CPUs to get their stats.
The desc should be protected with irq_lock_sparse().
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
---
kernel/irq/proc.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/kernel/irq/proc.c b/kernel/irq/proc.c
index e8f374971e37..bbc4004b74bc 100644
--- a/kernel/irq/proc.c
+++ b/kernel/irq/proc.c
@@ -544,17 +544,22 @@ int show_interrupts(struct seq_file *p, void *v)
if (!desc)
goto outsparse;
- raw_spin_lock_irqsave(&desc->lock, flags);
for_each_online_cpu(j)
any_count |= kstat_irqs_cpu(i, j);
+
action = desc->action;
- if ((!action || irq_desc_is_chained(desc)) && !any_count)
- goto out;
+ if (!any_count) {
+ raw_spin_lock_irqsave(&desc->lock, flags);
+ if (!action || irq_desc_is_chained(desc))
+ goto out;
+ raw_spin_unlock_irqrestore(&desc->lock, flags);
+ }
seq_printf(p, "%*d: ", prec, i);
for_each_online_cpu(j)
seq_printf(p, "%10u ", kstat_irqs_cpu(i, j));
+ raw_spin_lock_irqsave(&desc->lock, flags);
if (desc->irq_data.chip) {
if (desc->irq_data.chip->irq_print_chip)
desc->irq_data.chip->irq_print_chip(&desc->irq_data, p);
--
2.16.3
next reply other threads:[~2018-04-05 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 11:53 Nicholas Piggin [this message]
2018-04-26 20:24 ` Thomas Gleixner
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=20180405115313.29821-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®