mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chuyi Zhou" <zhouchuyi@bytedance.com>
To: "Nadav Amit" <nadav.amit@gmail.com>,
	 "Dave Hansen" <dave.hansen@intel.com>
Cc: <tglx@kernel.org>, <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>,
	 <bigeasy@linutronix.de>, <clrkwllms@kernel.org>,
	<rostedt@goodmis.org>,  <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 10/12] x86/mm: Move flush_tlb_info back to the stack
Date: Fri, 5 Jun 2026 10:54:53 +0800	[thread overview]
Message-ID: <ea4d667d-ef5d-4938-8057-062744d2ad81@bytedance.com> (raw)
In-Reply-To: <A43FB43A-9049-48EA-84B6-6DE09313A841@gmail.com>

On 2026-06-05 5:21 a.m., Nadav Amit wrote:
> 
> 
>> On 5 Jun 2026, at 0:16, Dave Hansen <dave.hansen@intel.com> wrote:
>>
>> On 6/4/26 14:11, Nadav Amit wrote:
>>>
>>> That's what led us to move flush_tlb_info into a per-cpu struct (preemption
>>> was disabled at that time, so there was no trade-off). Now that Zhou claims
>>> that disabling the preemption is a pain-point, and therefore does not want
>>> to set flush_tlb_info per-cpu, the solution we've landed on is to put it back
>>> on the stack - avoiding the need for a single flush_tlb_info that depends on
>>> preemption being disabled — while limiting the alignment to 64 bytes so the
>>> stack doesn't grow out of control.
>>
>> OK, cool. That's great info for a Link: tag. It also seems like you're
>> happy with this, so would a ack/review tag be appropriate to provide?
> 
> Ack tag is fine with me (there’s already suggested-by tag). For reviewed-by
> I should look a bit more thoroughly...

Thanks Dave and Nadav.

Yes, I agree the changelog should be reworded. I did not mean to
question Nadav's original patch or the benchmark methodology. The
per-cpu storage made sense when preemption was disabled, especially 
after the earlier stack-growth issue with cacheline-aligned on-stack 
storage.

I will update the changelog to describe that history explicitly: the
old stack-aligned version could grow the stack too much on some configs,
which led to the per-cpu storage, while this series needs to remove the
single per-cpu flush_tlb_info dependency as preparation for shortening 
the preemption-disabled window. The proposed compromise is to put it 
back on the stack, but cap the alignment at 64 bytes.


I will also split this into smaller patches in v7:

     1. refactor the flush_tlb_info helper so initialization can use
        caller-provided storage, without changing the current per-cpu
        storage;
     2. add the capped alignment for struct flush_tlb_info;
     3. move the actual flush_tlb_info storage from per-cpu back to the
        stack.

Nadav, thanks for the ack. I will add this in the next version.

  reply	other threads:[~2026-06-05  2:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28 15:13 [PATCH v6 00/12] Allow preemption during IPI completion waiting to improve real-time performance Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 01/12] smp: Disable preemption explicitly in __csd_lock_wait Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 02/12] smp: Enable preemption early in smp_call_function_single Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 03/12] smp: Refactor remote CPU selection in smp_call_function_any() Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 04/12] smp: Use task-local IPI cpumask in smp_call_function_many_cond() Chuyi Zhou
2026-06-03 10:54   ` Sebastian Andrzej Siewior
2026-06-03 11:48     ` Chuyi Zhou
2026-06-03 12:21       ` Sebastian Andrzej Siewior
2026-05-28 15:13 ` [PATCH v6 05/12] smp: Alloc percpu csd data in smpcfd_prepare_cpu() only once Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 06/12] smp: Enable preemption early in smp_call_function_many_cond Chuyi Zhou
2026-06-03 11:00   ` Sebastian Andrzej Siewior
2026-06-03 11:54     ` Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 07/12] smp: Remove preempt_disable from smp_call_function Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 08/12] smp: Remove preempt_disable from on_each_cpu_cond_mask Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 09/12] scftorture: Remove preempt_disable in scftorture_invoke_one Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 10/12] x86/mm: Move flush_tlb_info back to the stack Chuyi Zhou
2026-06-04 20:54   ` Dave Hansen
2026-06-04 21:11     ` Nadav Amit
2026-06-04 21:16       ` Dave Hansen
2026-06-04 21:21         ` Nadav Amit
2026-06-05  2:54           ` Chuyi Zhou [this message]
2026-05-28 15:13 ` [PATCH v6 11/12] x86/mm: Enable preemption during native_flush_tlb_multi Chuyi Zhou
2026-06-04 21:15   ` Dave Hansen
2026-06-05  3:36     ` Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 12/12] x86/mm: Enable preemption during flush_tlb_kernel_range Chuyi Zhou
2026-06-04 21:21   ` Dave Hansen
2026-06-05  3:51     ` Chuyi Zhou
2026-05-28 19:47 ` [PATCH v6 00/12] Allow preemption during IPI completion waiting to improve real-time performance Paul E. McKenney
2026-05-29  3:22   ` Chuyi Zhou
2026-05-29  6:41     ` Sebastian Andrzej Siewior
2026-06-03 11:02 ` 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=ea4d667d-ef5d-4938-8057-062744d2ad81@bytedance.com \
    --to=zhouchuyi@bytedance.com \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=clrkwllms@kernel.org \
    --cc=dave.hansen@intel.com \
    --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@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®