惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

月光博客
月光博客
有赞技术团队
有赞技术团队
S
SegmentFault 最新的问题
宝玉的分享
宝玉的分享
量子位
小众软件
小众软件
The Cloudflare Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
大猫的无限游戏
大猫的无限游戏
C
Check Point Blog
G
Google Developers Blog
博客园 - 叶小钗
H
Help Net Security
Jina AI
Jina AI
Y
Y Combinator Blog
Last Week in AI
Last Week in AI
GbyAI
GbyAI
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Apple Machine Learning Research
Apple Machine Learning Research
MyScale Blog
MyScale Blog
T
Tailwind CSS Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Vercel News
Vercel News

LWN.net comments

blocking algif_aead side effects? tcmalloc's weird hack [LWN.net] Fixed? [LWN.net] mpd [LWN.net] Userspace AX.25 [LWN.net] RIP [LWN.net] My two cents... [LWN.net] pipx [LWN.net] Tragedy [LWN.net] A young man destined for glory [LWN.net] And 'less' won't let you search [LWN.net] A great loss [LWN.net] Sad and shocking news [LWN.net] Easy migration from Clementine [LWN.net] Sad coincidence [LWN.net] GNOME is actually usable thanks to Seth et al [LWN.net] Sad news :( [LWN.net] armhf supports preempt_rt [LWN.net] MusicBrainz accurracy [LWN.net] On open source maintainership [LWN.net] Let's stop here [LWN.net] Not a new thing [LWN.net] uv is indeed great pgmoneta Some comments on this on a Postgres blog feed [LWN.net] uv [LWN.net] going to Debian [LWN.net] Upgrading 64-bit-capable systems to 64-bit kernels? [LWN.net] Free Software foundations Maintainers can wait for code review but not for publish review?
why did PREEMPT_LAZY caused more preemptions than PREEMPT...
rharjani · 2026-04-18 · via LWN.net comments

why did PREEMPT_LAZY caused more preemptions than PREEMPT_NONE with THP disabled?

Posted Apr 18, 2026 2:22 UTC (Sat) by rharjani (subscriber, #87278)
Parent article: The 7.0 scheduler regression that wasn't

I guess from above it still wasn't fully clear why PREEMPT_LAZY caused more preemptions than PREEMPT_NONE with THP disabled (or maybe it was obvious for few).

My assumption there is -

With THP disabled, the workload takes many more page faults which serializes on the page table spinlock. This means more preempt_disable() / preempt_enable() pairs for this type of workload. Since preempt_enable() is a preemption point under PREEMPT_LAZY but a no-op under PREEMPT_NONE, maybe this gives far more preemption opportunities under PREEMPT_LAZY (especially since the workload was CPU-intensive and ran well past the scheduler tick that would have escalated TIF_NEED_RESCHED_LAZY to TIF_NEED_RESCHED)