From: David Rientjes <rientjes@google.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch -mm] mm, oom: remove oom_lock from exit_mmap
Date: Mon, 16 Jul 2018 21:22:43 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1807162121040.157949@chino.kir.corp.google.com> (raw)
In-Reply-To: <44d26c25-6e09-49de-5e90-3c16115eb337@i-love.sakura.ne.jp>
On Sat, 14 Jul 2018, Tetsuo Handa wrote:
> David is making changes using timeout based back off (in linux-next.git)
> which is inappropriately trying to use MMF_UNSTABLE for two purposes.
>
If you believe there is a problem with the use of MMF_UNSTABLE as it sits
in -mm, please follow up directly in the thread that proposed the patch.
I have seen two replies to that thread from you: one that incorporates it
into your work, and one that links to a verison of my patch in your
patchset. I haven't seen a concern raised about the use of MMF_UNSTABLE,
but perhaps it's somewhere in the 10,000 other emails about the oom
killer.
next prev parent reply other threads:[~2018-07-17 4:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 21:34 [patch -mm] mm, oom: remove oom_lock from exit_mmap David Rientjes
2018-07-13 6:20 ` Tetsuo Handa
2018-07-13 14:26 ` Michal Hocko
2018-07-13 21:18 ` Tetsuo Handa
2018-07-16 6:13 ` Michal Hocko
2018-07-16 7:04 ` Tetsuo Handa
2018-07-16 7:44 ` Michal Hocko
2018-07-16 10:38 ` Tetsuo Handa
2018-07-16 11:15 ` Michal Hocko
2018-07-17 4:22 ` David Rientjes [this message]
2018-07-17 4:14 ` David Rientjes
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=alpine.DEB.2.21.1807162121040.157949@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.