From: Rik van Riel <riel@surriel.com>
To: linux-kernel@vger.kernel.org
Cc: Song Liu <songliubraving@fb.com>,
kernel-team@fb.com, mingo@redhat.com, luto@kernel.org,
tglx@linutronix.de, x86@kernel.org
Subject: [PATCH] x86,switch_mm: skip atomic operations for init_mm
Date: Fri, 1 Jun 2018 08:28:11 -0400 [thread overview]
Message-ID: <20180601082811.4c0d33ba@imladris.surriel.com> (raw)
Song noticed switch_mm_irqs_off taking a lot of CPU time in recent
kernels,using 2.4% of a 48 CPU system during a netperf to localhost run.
Digging into the profile, we noticed that cpumask_clear_cpu and
cpumask_set_cpu together take about half of the CPU time taken by
switch_mm_irqs_off.
However, the CPUs running netperf end up switching back and forth
between netperf and the idle task, which does not require changes
to the mm_cpumask. Furthermore, the init_mm cpumask ends up being
the most heavily contended one in the system.`
Skipping cpumask_clear_cpu and cpumask_set_cpu for init_mm
(mostly the idle task) reduced CPU use of switch_mm_irqs_off
from 2.4% of the CPU to 1.9% of the CPU, with the following
netperf commandline:
./super_netperf 300 -P 0 -t TCP_RR -p 8888 -H kerneltest008.09.atn1 -l 30 \
-- -r 300,300 -o -s 1M,1M -S 1M,1M
perf output w/o this patch:
1.26% netserver [kernel.vmlinux] [k] switch_mm_irqs_off
1.17% swapper [kernel.vmlinux] [k] switch_mm_irqs_off
perf output w/ this patch:
1.01% swapper [kernel.vmlinux] [k] switch_mm_irqs_off
0.88% netserver [kernel.vmlinux] [k] switch_mm_irqs_off
Netperf throughput is about the same before and after.
Signed-off-by: Rik van Riel <riel@surriel.com>
Reported-and-tested-by: Song Liu <songliubraving@fb.com>
---
arch/x86/mm/tlb.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/x86/mm/tlb.c b/arch/x86/mm/tlb.c
index e055d1a06699..c8f9c550f7ec 100644
--- a/arch/x86/mm/tlb.c
+++ b/arch/x86/mm/tlb.c
@@ -288,12 +288,14 @@ void switch_mm_irqs_off(struct mm_struct *prev, struct mm_struct *next,
/* Stop remote flushes for the previous mm */
VM_WARN_ON_ONCE(!cpumask_test_cpu(cpu, mm_cpumask(real_prev)) &&
real_prev != &init_mm);
- cpumask_clear_cpu(cpu, mm_cpumask(real_prev));
+ if (real_prev != &init_mm)
+ cpumask_clear_cpu(cpu, mm_cpumask(real_prev));
/*
* Start remote flushes and then read tlb_gen.
*/
- cpumask_set_cpu(cpu, mm_cpumask(next));
+ if (next != &init_mm)
+ cpumask_set_cpu(cpu, mm_cpumask(next));
next_tlb_gen = atomic64_read(&next->context.tlb_gen);
choose_new_asid(next, next_tlb_gen, &new_asid, &need_flush);
next reply other threads:[~2018-06-01 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 12:28 Rik van Riel [this message]
2018-06-01 15:11 ` Andy Lutomirski
2018-06-01 18:22 ` Rik van Riel
2018-06-01 18:48 ` Mike Galbraith
2018-06-01 19:43 ` Rik van Riel
2018-06-01 20:03 ` Andy Lutomirski
2018-06-01 20:35 ` Rik van Riel
2018-06-01 21:21 ` Andy Lutomirski
2018-06-01 22:13 ` Rik van Riel
2018-06-02 3:35 ` Andy Lutomirski
2018-06-02 5:04 ` Rik van Riel
2018-06-02 20:14 ` Andy Lutomirski
2018-06-03 0:51 ` Song Liu
2018-06-03 1:38 ` Rik van Riel
2018-06-06 18:17 ` Andy Lutomirski
2018-06-06 19:00 ` Rik van Riel
2018-06-06 19:23 ` Andy Lutomirski
2018-06-02 3:39 ` Mike Galbraith
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=20180601082811.4c0d33ba@imladris.surriel.com \
--to=riel@surriel.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®