Re: [RFC PATCH] mm/oom_kill: allow oom kill allocating task for non-global case

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Michal Hocko <mhocko@xxxxxxxx>
Subject: Re: [RFC PATCH] mm/oom_kill: allow oom kill allocating task for non-global case
From: Aaron Tomlin <atomlin@xxxxxxxxxx>
Date: Mon, 7 Jun 2021 22:17:47 +0100
Cc: linux-mm@xxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, vbabka@xxxxxxx, llong@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <YL5tBQ3utMzUkHF3@dhcp22.suse.cz>
References: <20210607163103.632681-1-atomlin@redhat.com> <YL5tBQ3utMzUkHF3@dhcp22.suse.cz>

On Mon 2021-06-07 21:01 +0200, Michal Hocko wrote:
> On Mon 07-06-21 17:31:03, Aaron Tomlin wrote:
> This is a global oom policy not a memcg specific one so a historical
> behavior would change. So I do not think we can change that.

I see. Fair enough.


-- 
Aaron Tomlin

References:
- [RFC PATCH] mm/oom_kill: allow oom kill allocating task for non-global case
  - From: Aaron Tomlin
- Re: [RFC PATCH] mm/oom_kill: allow oom kill allocating task for non-global case
  - From: Michal Hocko

Prev by Date: [RFC PATCH v2 5/8] drm/amdkfd: generic type as sys mem on migration to ram
Next by Date: Re: [PATCH Part1 RFC v3 00/22] Add AMD Secure Nested Paging (SEV-SNP) Guest Support
Previous by thread: Re: [RFC PATCH] mm/oom_kill: allow oom kill allocating task for non-global case
Next by thread: split_huge_page_to_list() races with page_mapcount() on migration entry in smaps code? [was: Re: [syzbot] kernel BUG in __page_mapcount]
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux