From: Frederic Weisbecker <frederic@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Valentin Schneider <vschneid@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Michal Hocko <mhocko@kernel.org>,
linux-mm@kvack.org, Ingo Molnar <mingo@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/6 v4] sched/mm: LRU drain flush on nohz_full
Date: Thu, 3 Jul 2025 16:07:11 +0200 [thread overview]
Message-ID: <20250703140717.25703-1-frederic@kernel.org> (raw)
When LRUs are pending, the drain can be triggered remotely, whether the
remote CPU is running in userspace in nohz_full mode or not. This kind
of noise is expected to be caused by preparatory work before a task
runs isolated in userspace. This patchset is a proposal to flush that
before the task starts its critical work in userspace.
Changes since v3:
* Apply review from Oleg and K Prateek Nayak (handle io_uring kthreads
and use guard)
* Confine this into a new CONFIG_NO_HZ_FULL_WORK because it is still
experimental.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
task/work-v4
HEAD: 87896fa0dc36b421533c9dc85dd32b61eaff887b
Thanks,
Frederic
---
Frederic Weisbecker (6):
task_work: Provide means to check if a work is queued
sched/fair: Use task_work_queued() on numa_work
sched: Use task_work_queued() on cid_work
tick/nohz: Move nohz_full related fields out of hot task struct's places
sched/isolation: Introduce isolated task work
mm: Drain LRUs upon resume to userspace on nohz_full CPUs
include/linux/pagevec.h | 18 ++----------------
include/linux/sched.h | 18 ++++++++++++------
include/linux/sched/isolation.h | 17 +++++++++++++++++
include/linux/swap.h | 1 +
include/linux/task_work.h | 12 ++++++++++++
kernel/sched/core.c | 6 ++----
kernel/sched/fair.c | 5 +----
kernel/sched/isolation.c | 26 ++++++++++++++++++++++++++
kernel/sched/sched.h | 1 +
kernel/task_work.c | 9 +++++++--
kernel/time/Kconfig | 12 ++++++++++++
mm/swap.c | 30 +++++++++++++++++++++++++++++-
12 files changed, 122 insertions(+), 33 deletions(-)
next reply other threads:[~2025-07-03 14:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 14:07 Frederic Weisbecker [this message]
2025-07-03 14:07 ` [PATCH 1/6] task_work: Provide means to check if a work is queued Frederic Weisbecker
2025-07-03 14:07 ` [PATCH 2/6] sched/fair: Use task_work_queued() on numa_work Frederic Weisbecker
2025-07-03 14:07 ` [PATCH 3/6] sched: Use task_work_queued() on cid_work Frederic Weisbecker
2025-07-17 16:32 ` Valentin Schneider
2025-07-03 14:07 ` [PATCH 4/6] tick/nohz: Move nohz_full related fields out of hot task struct's places Frederic Weisbecker
2025-07-17 16:32 ` Valentin Schneider
2025-07-03 14:07 ` [PATCH 5/6] sched/isolation: Introduce isolated task work Frederic Weisbecker
2025-07-17 17:29 ` Vlastimil Babka
2025-07-18 9:52 ` Valentin Schneider
2025-07-18 14:23 ` Frederic Weisbecker
2025-07-03 14:07 ` [PATCH 6/6] mm: Drain LRUs upon resume to userspace on nohz_full CPUs Frederic Weisbecker
2025-07-03 14:24 ` Michal Hocko
2025-07-03 14:28 ` Matthew Wilcox
2025-07-03 16:12 ` Michal Hocko
2025-07-17 19:33 ` Vlastimil Babka
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=20250703140717.25703-1-frederic@kernel.org \
--to=frederic@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=vschneid@redhat.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;
as well as URLs for NNTP newsgroup(s).