[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YqIXn0V3dEvGPZ1h@dhcp22.suse.cz>
Date: Thu, 9 Jun 2022 17:54:07 +0200
From: Michal Hocko <mhocko@...e.com>
To: Christian König <christian.koenig@....com>
Cc: Felix Kuehling <felix.kuehling@....com>,
Christian König
<ckoenig.leichtzumerken@...il.com>, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org, intel-gfx@...ts.freedesktop.org,
amd-gfx@...ts.freedesktop.org, nouveau@...ts.freedesktop.org,
linux-tegra@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, alexander.deucher@....com, daniel@...ll.ch,
viro@...iv.linux.org.uk, akpm@...ux-foundation.org,
hughd@...gle.com, andrey.grodzovsky@....com
Subject: Re: [PATCH 03/13] mm: shmem: provide oom badness for shmem files
On Thu 09-06-22 17:22:14, Christian König wrote:
[...]
> Those files were never part of any filesystem in the first place, so by
> killing all the process referencing them you can indeed free the memory
> locked by them.
Yes, this would require the oom killer to understand that all processes
referencing that file are killed. Theoretically possible but I am not
sure a feasible solution.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists