From: Waiman Long <llong@redhat.com>
To: Michal Hocko <mhocko@suse.com>, Waiman Long <llong@redhat.com>
Cc: Shakeel Butt <shakeelb@google.com>,
Aaron Tomlin <atomlin@redhat.com>, Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] mm/oom_kill: allow oom kill allocating task for non-global case
Date: Mon, 7 Jun 2021 16:44:09 -0400 [thread overview]
Message-ID: <353d012f-e8d4-c54c-b33e-54737e1a0115@redhat.com> (raw)
In-Reply-To: <YL57rLFwAo7EpYeH@dhcp22.suse.cz>
On 6/7/21 4:03 PM, Michal Hocko wrote:
> On Mon 07-06-21 21:36:47, Michal Hocko wrote:
>> On Mon 07-06-21 15:18:38, Waiman Long wrote:
> [...]
>>> A partial OOM report below:
>> Do you happen to have the full report?
>>
>>> [ 8221.433608] memory: usage 21280kB, limit 204800kB, failcnt 49116
>>> :
>>> [ 8227.239769] [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name
>>> [ 8227.242495] [1611298] 0 1611298 35869 635 167936 0 -1000 conmon
>>> [ 8227.242518] [1702509] 0 1702509 35869 701 176128 0 -1000 conmon
>>> [ 8227.242522] [1703345] 1001050000 1703294 183440 0 2125824 0 999 node
>>> [ 8227.242706] Out of memory and no killable processes...
>>> [ 8227.242731] node invoked oom-killer: gfp_mask=0x6000c0(GFP_KERNEL), nodemask=(null), order=0, oom_score_adj=999
> Btw it is surprising to not see _GFP_ACCOUNT here.
There are a number of OOM kills in the kernel log and none of the tasks
that invoke oom-killer has _GFP_ACCOUNT flag set.
Regards,
Longman
next prev parent reply other threads:[~2021-06-07 20:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 16:31 Aaron Tomlin
2021-06-07 16:42 ` Waiman Long
2021-06-07 18:43 ` Shakeel Butt
2021-06-07 18:51 ` Waiman Long
2021-06-07 19:04 ` Michal Hocko
2021-06-07 19:18 ` Waiman Long
2021-06-07 19:36 ` Michal Hocko
2021-06-07 20:03 ` Michal Hocko
2021-06-07 20:44 ` Waiman Long [this message]
2021-06-08 6:22 ` Michal Hocko
2021-06-08 9:39 ` Aaron Tomlin
2021-06-08 10:00 ` Aaron Tomlin
2021-06-08 13:58 ` Michal Hocko
2021-06-08 15:22 ` Tetsuo Handa
2021-06-08 16:17 ` Michal Hocko
2021-06-09 14:35 ` Aaron Tomlin
2021-06-10 10:00 ` Michal Hocko
2021-06-10 12:23 ` Aaron Tomlin
2021-06-10 12:43 ` Michal Hocko
2021-06-10 13:36 ` Aaron Tomlin
2021-06-10 14:06 ` Tetsuo Handa
2021-06-07 20:42 ` Waiman Long
2021-06-07 21:16 ` Aaron Tomlin
2021-06-07 19:04 ` Shakeel Butt
2021-06-07 20:07 ` Waiman Long
2021-06-07 19:01 ` Michal Hocko
2021-06-07 19:26 ` Waiman Long
2021-06-07 19:47 ` Michal Hocko
2021-06-07 21:17 ` Aaron Tomlin
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=353d012f-e8d4-c54c-b33e-54737e1a0115@redhat.com \
--to=llong@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=shakeelb@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