From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Andrew Morton <akpm@linux-foundation.org>,
David Rientjes <rientjes@google.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] mm, oom: stop reclaiming if GFP_ATOMIC will start failing soon
Date: Sun, 26 Apr 2020 12:04:56 +0900 [thread overview]
Message-ID: <c2c2f453-9cb3-72b9-a484-03652e8ce10e@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20200425172706.26b5011293e8dc77b1dccaf3@linux-foundation.org>
On 2020/04/26 9:27, Andrew Morton wrote:
> Well, what's really going on here?
>
> Is networking potentially consuming an unbounded amount of memory? If
> so, then killing a process will just cause networking to consume more
> memory then hit against the same thing. So presumably the answer is
> "no, the watermarks are inappropriately set for this workload".
Maybe somebody is abusing __GFP_MEMALLOC allocations. David, please include whole
context (e.g. which function from which process) instead of only memory stat lines.
next prev parent reply other threads:[~2020-04-26 3:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 20:48 David Rientjes
2020-04-25 0:32 ` Tetsuo Handa
2020-04-26 0:27 ` Andrew Morton
2020-04-26 3:04 ` Tetsuo Handa [this message]
2020-04-27 3:12 ` David Rientjes
2020-04-27 5:03 ` Tetsuo Handa
2020-04-27 20:30 ` Andrew Morton
2020-04-27 23:03 ` David Rientjes
2020-04-27 23:35 ` Andrew Morton
2020-04-28 7:43 ` Michal Hocko
2020-04-29 8:31 ` peter enderborg
2020-04-29 9:00 ` Michal Hocko
2020-04-28 9:38 ` Vlastimil Babka
2020-04-28 21:48 ` David Rientjes
2020-04-28 23:37 ` Tetsuo Handa
2020-04-29 7:51 ` Vlastimil Babka
2020-04-29 9:04 ` Michal Hocko
2020-04-29 10:45 ` Tetsuo Handa
2020-04-29 11:43 ` Michal Hocko
2020-04-27 8:20 ` peter enderborg
2020-04-27 15:01 ` 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=c2c2f453-9cb3-72b9-a484-03652e8ce10e@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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