Linux Documentation
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Aditya Sharma <adi.sharma@zohomail.in>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	"Liam R . Howlett" <liam@infradead.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>,
	David Rientjes <rientjes@google.com>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Kees Cook <kees@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Valentin Schneider <vschneid@redhat.com>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	linux-mm <linux-mm@kvack.org>,
	linux-doc <linux-doc@vger.kernel.org>,
	linux-trace-kernel <linux-trace-kernel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	imbrenda <imbrenda@linux.ibm.com>
Subject: Re: [RFC PATCH 0/7] mm: defer address-space teardown of large exiting processes to a kthread
Date: Tue, 21 Jul 2026 12:19:57 +0200	[thread overview]
Message-ID: <d6c3eba3-c596-4903-b298-ac6f424d639c@kernel.org> (raw)
In-Reply-To: <19f80cb1ed8.13fd666243425.2308143427066829733@zohomail.in>

[...]

> says that the s390 case was addressed with KVM specific async destruction,
> but what you point to is QEMU's shadow process. I will correct that in v2.

CLONE_VM seems to work for the use cases you had in mind.

There would have to be a *pretty* convincing story why we would want more
complexity in the kernel to handle this.

Some smaller performance improvements are not worth it.
-- 
Cheers,

David

  reply	other threads:[~2026-07-21 10:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-19 18:54 [RFC PATCH 0/7] mm: defer address-space teardown of large exiting processes to a kthread Aditya Sharma
2026-07-19 18:54 ` [RFC PATCH 1/7] mm: add CONFIG_ASYNC_MM_TEARDOWN scaffolding for off-CPU exit teardown Aditya Sharma
2026-07-19 18:54 ` [RFC PATCH 2/7] mm: dispatch __mmput() to an mm_reaper kthread via llist Aditya Sharma
2026-07-19 18:54 ` [RFC PATCH 3/7] mm/oom_kill: mark an OOM victim's mm with MMF_OOM_TARGETED Aditya Sharma
2026-07-19 18:54 ` [RFC PATCH 4/7] mm: gate async teardown on RSS with pending-pages backpressure Aditya Sharma
2026-07-19 18:54 ` [RFC PATCH 5/7] mm: add runtime toggle and sysctls for async teardown Aditya Sharma
2026-07-19 18:54 ` [RFC PATCH 6/7] mm: add tracepoints and vmstat counters " Aditya Sharma
2026-07-21 21:17   ` Steven Rostedt
2026-07-23 18:22     ` Aditya Sharma
2026-07-19 18:54 ` [RFC PATCH 7/7] exit: route exit_mm()'s final mmput() through mmput_exit() Aditya Sharma
2026-07-19 22:28 ` [RFC PATCH 0/7] mm: defer address-space teardown of large exiting processes to a kthread Liam R . Howlett
2026-07-20 18:38   ` Aditya Sharma
2026-07-20  8:13 ` David Hildenbrand (Arm)
2026-07-20 18:30   ` Aditya Sharma
2026-07-21 10:19     ` David Hildenbrand (Arm) [this message]
2026-07-23 18:20       ` Aditya Sharma

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=d6c3eba3-c596-4903-b298-ac6f424d639c@kernel.org \
    --to=david@kernel.org \
    --cc=adi.sharma@zohomail.in \
    --cc=akpm@linux-foundation.org \
    --cc=bsegall@google.com \
    --cc=corbet@lwn.net \
    --cc=dietmar.eggemann@arm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=juri.lelli@redhat.com \
    --cc=kees@kernel.org \
    --cc=kprateek.nayak@amd.com \
    --cc=liam@infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=ljs@kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mgorman@suse.de \
    --cc=mhiramat@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rientjes@google.com \
    --cc=rostedt@goodmis.org \
    --cc=rppt@kernel.org \
    --cc=shakeel.butt@linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --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