From: Michal Hocko <mhocko@suse.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
thuth@redhat.com, frankja@linux.ibm.com, borntraeger@de.ibm.com,
Ulrich.Weigand@de.ibm.com, david@redhat.com, ultrachin@163.com,
akpm@linux-foundation.org, vbabka@suse.cz, brookxu.cn@gmail.com,
xiaoggchen@tencent.com, linuszeng@tencent.com,
yihuilu@tencent.com, daniel.m.jordan@oracle.com, axboe@kernel.dk,
legion@kernel.org, peterz@infradead.org, aarcange@redhat.com,
christian@brauner.io, tglx@linutronix.de
Subject: Re: [RFC v1 2/4] kernel/fork.c: implement new process_mmput_async syscall
Date: Mon, 15 Nov 2021 11:43:57 +0100 [thread overview]
Message-ID: <YZI57bFLvBptKkYj@dhcp22.suse.cz> (raw)
In-Reply-To: <20211112175309.7e0fe52a@p-imbrenda>
On Fri 12-11-21 17:53:09, Claudio Imbrenda wrote:
[...]
> Of course, but this also means that it's not possible to stop the OOM
> killer while the teardown is in progress,
Blocking the OOM killer and depend on the userspace to make a forward
progress is not acceptable solution.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-11-15 10:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 9:50 [RFC v1 0/4] Two alternatives for mm async teardown Claudio Imbrenda
2021-11-11 9:50 ` [RFC v1 1/4] add arch mmput hook in exit.c Claudio Imbrenda
2021-11-11 9:50 ` [RFC v1 1/4] exit: add arch mmput hook in exit_mm Claudio Imbrenda
2021-11-11 18:43 ` Eric W. Biederman
2021-11-11 9:50 ` [RFC v1 2/4] kernel/fork.c: implement new process_mmput_async syscall Claudio Imbrenda
2021-11-11 19:20 ` Eric W. Biederman
2021-11-12 9:27 ` Claudio Imbrenda
2021-11-12 9:34 ` Claudio Imbrenda
2021-11-12 14:57 ` Eric W. Biederman
2021-11-12 16:53 ` Claudio Imbrenda
2021-11-15 10:43 ` Michal Hocko [this message]
2021-11-11 9:50 ` [RFC v1 3/4] mm: wire up the " Claudio Imbrenda
2021-11-11 9:50 ` [RFC v1 4/4] kernel/fork.c: process_mmput_async: stop OOM while freeing memory Claudio Imbrenda
2021-11-12 10:15 ` [RFC v1 0/4] Two alternatives for mm async teardown Michal Hocko
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=YZI57bFLvBptKkYj@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=brookxu.cn@gmail.com \
--cc=christian@brauner.io \
--cc=daniel.m.jordan@oracle.com \
--cc=david@redhat.com \
--cc=ebiederm@xmission.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=legion@kernel.org \
--cc=linuszeng@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thuth@redhat.com \
--cc=ultrachin@163.com \
--cc=vbabka@suse.cz \
--cc=xiaoggchen@tencent.com \
--cc=yihuilu@tencent.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).