From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Chuyi Zhou <zhouchuyi@bytedance.com>
Cc: tglx@linutronix.de, mingo@redhat.com, luto@kernel.org,
peterz@infradead.org, paulmck@kernel.org, muchun.song@linux.dev,
bp@alien8.de, dave.hansen@linux.intel.com, pbonzini@redhat.com,
clrkwllms@kernel.org, rostedt@goodmis.org, nadav.amit@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v5 06/12] smp: Enable preemption early in smp_call_function_many_cond
Date: Fri, 22 May 2026 12:08:35 +0200 [thread overview]
Message-ID: <20260522100835.rgqCLkwa@linutronix.de> (raw)
In-Reply-To: <20260513124524.2569867-7-zhouchuyi@bytedance.com>
On 2026-05-13 20:45:18 [+0800], Chuyi Zhou wrote:
> --- a/kernel/smp.c
> +++ b/kernel/smp.c
> @@ -861,10 +861,10 @@ static void smp_call_function_many_cond(const struct cpumask *mask,
> int nr_cpus = 0;
> bool run_remote = false;
>
> - lockdep_assert_preemption_disabled();
> -
> task_mask = smp_task_ipi_mask(current);
> - preemptible_wait = task_mask;
> + preemptible_wait = task_mask && preemptible();
Now that I stare at this again, why is preemptible() a thing here?
You care about doing put_cpu() below before csd_lock_wait(). This can
only be done if you get a cpumask from smp_task_ipi_mask(). If
preemption or interrupts is/are disabled then you still can use the
"private" cpumask and do the early put_cpu(). It simply is no
optimisation.
This basically reduces the check to a CONFIG_PREEMPTION=y kernel because
otherwise you have no cpumask. And this is not done on !SMP kernels.
smp_task_ipi_mask() is only used here so there is no need to export it
via headers.
> +
> + this_cpu = get_cpu();
> cfd = this_cpu_ptr(&cfd_data);
> cpumask = preemptible_wait ? task_mask : cfd->cpumask;
>
> @@ -946,6 +946,19 @@ static void smp_call_function_many_cond(const struct cpumask *mask,
> local_irq_restore(flags);
> }
>
> + /*
> + * We may block in csd_lock_wait() for a significant amount of time,
> + * especially when interrupts are disabled or with a large number of
> + * remote CPUs. Try to enable preemption before csd_lock_wait().
If interrupts are disabled there is no gain. Also we sort of expect
interrupts to be enabled here.
Waiting for completion can take time especially with many CPUs. On a
PREEMPTIBLE kernel a per-task cpumask is used to track CPUs with
pending IPI request. This allows to enable preemption and potentially
wait while allowing task preemption. On a !PREEMPTIBLE the cpumask is
shared and the call must block until completion to avoid modifications
by a another caller on this CPU.
> + *
> + * Use the task_mask instead of cfd->cpumask to avoid concurrency
> + * modification from tasks on the same cpu. If preemption occurs during
> + * csd_lock_wait, other concurrent smp_call_function_many_cond() calls
> + * will simply block until the previous csd->func() completes.
> + */
> + if (preemptible_wait)
> + put_cpu();
> +
> if (run_remote && wait) {
> for_each_cpu(cpu, cpumask) {
> call_single_data_t *csd;
> @@ -954,6 +967,9 @@ static void smp_call_function_many_cond(const struct cpumask *mask,
> csd_lock_wait(csd);
> }
> }
> +
> + if (!preemptible_wait)
> + put_cpu();
> }
>
> /**
Sebastian
next prev parent reply other threads:[~2026-05-22 10:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 12:45 [RESEND PATCH v5 00/12] Allow preemption during IPI completion waiting to improve real-time performance Chuyi Zhou
2026-05-13 12:45 ` [RESEND PATCH v5 01/12] smp: Disable preemption explicitly in __csd_lock_wait Chuyi Zhou
2026-05-13 12:45 ` [RESEND PATCH v5 02/12] smp: Enable preemption early in smp_call_function_single Chuyi Zhou
2026-05-13 12:45 ` [RESEND PATCH v5 03/12] smp: Refactor remote CPU selection in smp_call_function_any() Chuyi Zhou
2026-05-13 12:45 ` [RESEND PATCH v5 04/12] smp: Use task-local IPI cpumask in smp_call_function_many_cond() Chuyi Zhou
2026-05-21 15:26 ` Sebastian Andrzej Siewior
2026-05-21 16:00 ` Chuyi Zhou
2026-05-22 7:22 ` Sebastian Andrzej Siewior
2026-05-13 12:45 ` [RESEND PATCH v5 05/12] smp: Alloc percpu csd data in smpcfd_prepare_cpu() only once Chuyi Zhou
2026-05-13 12:45 ` [RESEND PATCH v5 06/12] smp: Enable preemption early in smp_call_function_many_cond Chuyi Zhou
2026-05-22 10:08 ` Sebastian Andrzej Siewior [this message]
2026-05-22 15:16 ` Chuyi Zhou
2026-05-13 12:45 ` [RESEND PATCH v5 07/12] smp: Remove preempt_disable from smp_call_function Chuyi Zhou
2026-05-13 12:45 ` [RESEND PATCH v5 08/12] smp: Remove preempt_disable from on_each_cpu_cond_mask Chuyi Zhou
2026-05-13 12:45 ` [RESEND PATCH v5 09/12] scftorture: Remove preempt_disable in scftorture_invoke_one Chuyi Zhou
2026-05-13 12:45 ` [RESEND PATCH v5 10/12] x86/mm: Move flush_tlb_info back to the stack Chuyi Zhou
2026-05-13 12:45 ` [RESEND PATCH v5 11/12] x86/mm: Enable preemption during native_flush_tlb_multi Chuyi Zhou
2026-05-13 12:45 ` [RESEND PATCH v5 12/12] x86/mm: Enable preemption during flush_tlb_kernel_range Chuyi Zhou
2026-05-22 10:48 ` Sebastian Andrzej Siewior
2026-05-26 3:25 ` Chuyi Zhou
2026-05-20 12:44 ` [RESEND PATCH v5 00/12] Allow preemption during IPI completion waiting to improve real-time performance Chuyi Zhou
2026-05-22 10:57 ` Sebastian Andrzej Siewior
2026-05-22 14:11 ` Steven Rostedt
2026-05-22 14:45 ` Sebastian Andrzej Siewior
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=20260522100835.rgqCLkwa@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=clrkwllms@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=muchun.song@linux.dev \
--cc=nadav.amit@gmail.com \
--cc=paulmck@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=zhouchuyi@bytedance.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
all inboxes | Powered by JetHome®