From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH 0/3] smp: Avoid memory allocation in on_each_cpu_cond()
Date: Fri, 17 Jan 2020 10:01:34 +0100 [thread overview]
Message-ID: <20200117090137.1205765-1-bigeasy@linutronix.de> (raw)
x86 is using on_each_cpu_cond_mask() in native_flush_tlb_others() in a
preempt disabled section. The memory allocation in
on_each_cpu_cond_mask() gives me a headache on RT.
This is an attempt to get rid of the memory allocation and potentially
accelerating the code path :)
Sebastian
next reply other threads:[~2020-01-17 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 9:01 Sebastian Andrzej Siewior [this message]
2020-01-17 9:01 ` [PATCH 1/3] smp: Use smp_cond_func_t as type for the conditional function Sebastian Andrzej Siewior
2020-01-24 19:45 ` [tip: smp/core] " tip-bot2 for Sebastian Andrzej Siewior
2020-01-17 9:01 ` [PATCH 2/3] smp: Add a smp_cond_func_t argument to smp_call_function_many() Sebastian Andrzej Siewior
2020-01-17 13:15 ` Peter Zijlstra
2020-01-17 14:41 ` [PATCH 2/3 v2] " Sebastian Andrzej Siewior
2020-01-24 19:45 ` [tip: smp/core] " tip-bot2 for Sebastian Andrzej Siewior
2020-01-27 8:39 ` [PATCH] smp: Remove superfluous cond_func check in smp_call_function_many_cond() Sebastian Andrzej Siewior
2020-01-28 14:46 ` [tip: smp/urgent] " tip-bot2 for Sebastian Andrzej Siewior
2020-01-17 9:01 ` [PATCH 3/3] smp: Remove allocation mask from on_each_cpu_cond.*() Sebastian Andrzej Siewior
2020-01-24 19:45 ` [tip: smp/core] " tip-bot2 for Sebastian Andrzej Siewior
2020-01-17 15:00 ` [PATCH 0/3] smp: Avoid memory allocation in on_each_cpu_cond() Peter Zijlstra
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=20200117090137.1205765-1-bigeasy@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).