From: "Chuyi Zhou" <zhouchuyi@bytedance.com>
To: "Peter Zijlstra" <peterz@infradead.org>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <luto@kernel.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 v2 10/12] x86/mm: Move flush_tlb_info back to the stack
Date: Thu, 5 Mar 2026 15:01:19 +0800 [thread overview]
Message-ID: <1aeb64e0-97bb-4b25-a0b7-435240dfbbd3@bytedance.com> (raw)
In-Reply-To: <20260302145848.GI1395266@noisy.programming.kicks-ass.net>
Hi Peter,
在 2026/3/2 22:58, Peter Zijlstra 写道:
> On Mon, Mar 02, 2026 at 03:52:14PM +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.
>>
>> From the perspective of improving kernel real-time performance, this patch
>> reverts flush_tlb_info back to stack variables. This is a preparation for
>> enabling preemption during TLB flush in next patch.
>
> This isn't properly justified. You've got to show that 'most' workloads
> are not adversely affected by this.
>
> Most people still swing towards performance most of the time.
I attempted to reproduce the microbenchmark mentioned in Commit
3db6d5a5ecaf ("x86/mm/tlb: Remove 'struct flush_tlb_info' from the
stack") using the script below.
The baseline was tip/sched/core: f74d204baf9f (sched/hrtick: Mark
hrtick_clear() as always used).
The test environment was an Ice Lake system (Intel(R) Xeon(R) Platinum
8336C) with 128 CPUs and 2 NUMA nodes.
Using the per-CPU flush_tlb_info showed only a very marginal performance
advantage, approximately 1%.
base on-stack
---- ---------
avg (usec/op) 5.9362 5.9956 (+1%)
stddev 0.0240 0.0096
I also tested with mmtest/stress-ng-madvise, which randomly calls
madvise on pages within a mmap range and triggers a large number of
high-frequency TLB flushes. However, I did not observe any significant
difference.
baseline on-stack
Amean bops-madvise-1 13.64 ( 0.00%) 13.56 ( 0.59%)
Amean bops-madvise-2 27.32 ( 0.00%) 27.26 ( 0.24%)
Amean bops-madvise-4 53.35 ( 0.00%) 53.54 ( -0.35%)
Amean bops-madvise-8 103.09 ( 0.00%) 103.30 ( -0.20%)
Amean bops-madvise-16 191.88 ( 0.00%) 191.75 ( 0.07%)
Amean bops-madvise-32 287.98 ( 0.00%) 291.01 * -1.05%*
Amean bops-madvise-64 365.84 ( 0.00%) 368.09 * -0.61%*
Amean bops-madvise-128 422.72 ( 0.00%) 423.47 ( -0.18%)
Amean bops-madvise-256 435.61 ( 0.00%) 435.63 ( -0.01%)
Thanks.
#define _GNU_SOURCE
#include <stdio.h>
#include <stdlib.h>
#include <pthread.h>
#include <sys/mman.h>
#include <sys/time.h>
#include <unistd.h>
#define NUM_OPS 1000000
#define NUM_THREADS 3
#define NUM_RUNS 5
#define PAGE_SIZE 4096
volatile int stop_threads = 0;
void *busy_wait_thread(void *arg) {
while (!stop_threads) {
__asm__ volatile ("nop");
}
return NULL;
}
long long get_usec() {
struct timeval tv;
gettimeofday(&tv, NULL);
return tv.tv_sec * 1000000LL + tv.tv_usec;
}
int main() {
pthread_t threads[NUM_THREADS];
char *addr;
int i, r;
addr = mmap(NULL, PAGE_SIZE, PROT_READ | PROT_WRITE, MAP_PRIVATE |
MAP_ANONYMOUS, -1, 0);
if (addr == MAP_FAILED) {
perror("mmap");
exit(1);
}
for (i = 0; i < NUM_THREADS; i++) {
if (pthread_create(&threads[i], NULL, busy_wait_thread, NULL)
!= 0) {
perror("pthread_create");
exit(1);
}
}
printf("Running benchmark: %d runs, %d ops each, %d background
threads\n", NUM_RUNS, NUM_OPS, NUM_THREADS);
for (r = 0; r < NUM_RUNS; r++) {
long long start, end;
start = get_usec();
for (i = 0; i < NUM_OPS; i++) {
addr[0] = 1;
if (madvise(addr, PAGE_SIZE, MADV_DONTNEED) != 0) {
perror("madvise");
exit(1);
}
}
end = get_usec();
double duration = (double)(end - start);
double avg_lat = duration / NUM_OPS;
printf("Run %d: Total time %.2f us, Avg latency %.4f us/op\n",
r + 1, duration, avg_lat);
}
stop_threads = 1;
for (i = 0; i < NUM_THREADS; i++) {
pthread_join(threads[i], NULL);
}
munmap(addr, PAGE_SIZE);
return 0;
}
next prev parent reply other threads:[~2026-03-05 7:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 7:52 [PATCH v2 00/12] Allow preemption during IPI completion waiting to improve real-time performance Chuyi Zhou
2026-03-02 7:52 ` [PATCH v2 01/12] smp: Disable preemption explicitly in __csd_lock_wait Chuyi Zhou
2026-03-02 7:52 ` [PATCH v2 02/12] smp: Enable preemption early in smp_call_function_single Chuyi Zhou
2026-03-02 7:52 ` [PATCH v2 03/12] smp: Remove get_cpu from smp_call_function_any Chuyi Zhou
2026-03-02 7:52 ` [PATCH v2 04/12] smp: Use on-stack cpumask in smp_call_function_many_cond Chuyi Zhou
2026-03-10 7:12 ` Muchun Song
2026-03-02 7:52 ` [PATCH v2 05/12] smp: Free call_function_data via RCU in smpcfd_dead_cpu Chuyi Zhou
2026-03-10 7:05 ` Muchun Song
2026-03-10 7:26 ` Chuyi Zhou
2026-03-02 7:52 ` [PATCH v2 06/12] smp: Enable preemption early in smp_call_function_many_cond Chuyi Zhou
2026-03-02 7:52 ` [PATCH v2 07/12] smp: Remove preempt_disable from smp_call_function Chuyi Zhou
2026-03-10 7:06 ` Muchun Song
2026-03-02 7:52 ` [PATCH v2 08/12] smp: Remove preempt_disable from on_each_cpu_cond_mask Chuyi Zhou
2026-03-10 7:06 ` Muchun Song
2026-03-02 7:52 ` [PATCH v2 09/12] scftorture: Remove preempt_disable in scftorture_invoke_one Chuyi Zhou
2026-03-02 7:52 ` [PATCH v2 10/12] x86/mm: Move flush_tlb_info back to the stack Chuyi Zhou
2026-03-02 14:58 ` Peter Zijlstra
2026-03-03 3:20 ` Chuyi Zhou
2026-03-05 7:01 ` Chuyi Zhou [this message]
2026-03-02 7:52 ` [PATCH v2 11/12] x86/mm: Enable preemption during native_flush_tlb_multi Chuyi Zhou
2026-03-02 7:52 ` [PATCH v2 12/12] x86/mm: Enable preemption during flush_tlb_kernel_range Chuyi Zhou
2026-03-10 6:35 ` kernel test robot
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=1aeb64e0-97bb-4b25-a0b7-435240dfbbd3@bytedance.com \
--to=zhouchuyi@bytedance.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 \
/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®