From: Nadav Amit <nadav.amit@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Chuyi Zhou <zhouchuyi@bytedance.com>,
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,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 10/12] x86/mm: Move flush_tlb_info back to the stack
Date: Wed, 18 Mar 2026 22:24:41 +0200 [thread overview]
Message-ID: <44F4BED1-D09A-40B3-BB2B-E2AFB0AF8D0D@gmail.com> (raw)
In-Reply-To: <20260318172143.ICooJ3-U@linutronix.de>
> On 18 Mar 2026, at 19:21, Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
>
> +Nadav, org post https://lore.kernel.org/all/20260318045638.1572777-11-zhouchuyi@bytedance.com/
>
> On 2026-03-18 12:56:36 [+0800], Chuyi Zhou wrote:
>> Commit 3db6d5a5ecaf ("x86/mm/tlb: Remove 'struct flush_tlb_info' from the
>> stack") converted flush_tlb_info from stack variable to per-CPU variable.
>> This brought about a performance improvement of around 3% in extreme test.
>> However, it also required that all flush_tlb* operations keep preemption
>> disabled entirely to prevent concurrent modifications of flush_tlb_info.
>> flush_tlb* needs to send IPIs to remote CPUs and synchronously wait for
>> all remote CPUs to complete their local TLB flushes. The process could
>> take tens of milliseconds when interrupts are disabled or with a large
>> number of remote CPUs.
> …
> PeterZ wasn't too happy to reverse this.
> The snippet below results in the following assembly:
>
> | 0000000000001ab0 <flush_tlb_kernel_range>:
> …
> | 1ac9: 48 89 e5 mov %rsp,%rbp
> | 1acc: 48 83 e4 c0 and $0xffffffffffffffc0,%rsp
> | 1ad0: 48 83 ec 40 sub $0x40,%rsp
>
> so it would align it properly which should result in the same cache-line
> movement. I'm not sure about the virtual-to-physical translation of the
> variables as in TLB misses since here we have a virtual mapped stack and
> there we have virtual mapped per-CPU memory.
>
> Here the below is my quick hack. Does this work, or still a now? I have
> no numbers so…
>
> diff --git a/arch/x86/include/asm/tlbflush.h b/arch/x86/include/asm/tlbflush.h
> index 5a3cdc439e38d..4a7f40c7f939a 100644
> --- a/arch/x86/include/asm/tlbflush.h
> +++ b/arch/x86/include/asm/tlbflush.h
> @@ -227,7 +227,7 @@ struct flush_tlb_info {
> u8 stride_shift;
> u8 freed_tables;
> u8 trim_cpumask;
> -};
> +} __aligned(SMP_CACHE_BYTES);
>
This would work, but you are likely to encounter the same problem PeterZ hit
when I did something similar: in some configurations SMP_CACHE_BYTES is very
large.
See https://lore.kernel.org/all/tip-780e0106d468a2962b16b52fdf42898f2639e0a0@git.kernel.org/
Maybe cap the alignment somehow? something like:
#if SMP_CACHE_BYTES > 64
#define FLUSH_TLB_INFO_ALIGN 64
#else
#define FLUSH_TLB_INFO_ALIGN SMP_CACHE_BYTES
#endif
And then use __aligned(FLUSH_TLB_INFO_ALIGN) ?
next prev parent reply other threads:[~2026-03-18 20:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 4:56 [PATCH v3 00/12] Allow preemption during IPI completion waiting to improve real-time performance Chuyi Zhou
2026-03-18 4:56 ` [PATCH v3 01/12] smp: Disable preemption explicitly in __csd_lock_wait Chuyi Zhou
2026-03-18 14:13 ` Steven Rostedt
2026-03-18 4:56 ` [PATCH v3 02/12] smp: Enable preemption early in smp_call_function_single Chuyi Zhou
2026-03-18 14:14 ` Steven Rostedt
2026-03-19 2:30 ` Chuyi Zhou
2026-03-18 4:56 ` [PATCH v3 03/12] smp: Remove get_cpu from smp_call_function_any Chuyi Zhou
2026-03-18 14:32 ` Steven Rostedt
2026-03-18 15:39 ` Sebastian Andrzej Siewior
2026-03-18 4:56 ` [PATCH v3 04/12] smp: Use on-stack cpumask in smp_call_function_many_cond Chuyi Zhou
2026-03-18 14:38 ` Steven Rostedt
2026-03-18 15:55 ` Sebastian Andrzej Siewior
2026-03-19 3:02 ` Chuyi Zhou
2026-03-18 4:56 ` [PATCH v3 05/12] smp: Free call_function_data via RCU in smpcfd_dead_cpu Chuyi Zhou
2026-03-18 16:19 ` Sebastian Andrzej Siewior
2026-03-19 7:48 ` Chuyi Zhou
2026-03-18 4:56 ` [PATCH v3 06/12] smp: Enable preemption early in smp_call_function_many_cond Chuyi Zhou
2026-03-18 16:55 ` Sebastian Andrzej Siewior
2026-03-19 3:46 ` Chuyi Zhou
2026-03-18 4:56 ` [PATCH v3 07/12] smp: Remove preempt_disable from smp_call_function Chuyi Zhou
2026-03-18 4:56 ` [PATCH v3 08/12] smp: Remove preempt_disable from on_each_cpu_cond_mask Chuyi Zhou
2026-03-18 4:56 ` [PATCH v3 09/12] scftorture: Remove preempt_disable in scftorture_invoke_one Chuyi Zhou
2026-03-18 4:56 ` [PATCH v3 10/12] x86/mm: Move flush_tlb_info back to the stack Chuyi Zhou
2026-03-18 17:21 ` Sebastian Andrzej Siewior
2026-03-18 20:24 ` Nadav Amit [this message]
2026-03-18 22:28 ` Nadav Amit
2026-03-19 8:49 ` Sebastian Andrzej Siewior
2026-03-19 10:37 ` Nadav Amit
2026-03-19 10:58 ` Sebastian Andrzej Siewior
2026-03-19 13:41 ` Chuyi Zhou
2026-03-19 14:40 ` Sebastian Andrzej Siewior
2026-03-20 14:33 ` Chuyi Zhou
2026-03-18 4:56 ` [PATCH v3 11/12] x86/mm: Enable preemption during native_flush_tlb_multi Chuyi Zhou
2026-03-18 4:56 ` [PATCH v3 12/12] x86/mm: Enable preemption during flush_tlb_kernel_range Chuyi Zhou
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=44F4BED1-D09A-40B3-BB2B-E2AFB0AF8D0D@gmail.com \
--to=nadav.amit@gmail.com \
--cc=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=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®