[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1403061254240.25499@chino.kir.corp.google.com>
Date: Thu, 6 Mar 2014 12:55:43 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: Tejun Heo <tj@...nel.org>
cc: Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...e.cz>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Christoph Lameter <cl@...ux-foundation.org>,
Pekka Enberg <penberg@...nel.org>,
Mel Gorman <mgorman@...e.de>, Oleg Nesterov <oleg@...hat.com>,
Rik van Riel <riel@...hat.com>,
Jianguo Wu <wujianguo@...wei.com>,
Tim Hockin <thockin@...gle.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, cgroups@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [patch 00/11] userspace out of memory handling
On Thu, 6 Mar 2014, Tejun Heo wrote:
> On Tue, Mar 04, 2014 at 07:58:38PM -0800, David Rientjes wrote:
> > This patchset implements userspace out of memory handling.
> >
> > It is based on v3.14-rc5. Individual patches will apply cleanly or you
> > may pull the entire series from
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rientjes/linux.git mm/oom
> >
> > When the system or a memcg is oom, processes running on that system or
> > attached to that memcg cannot allocate memory. It is impossible for a
> > process to reliably handle the oom condition from userspace.
>
> ISTR the conclusion last time was nack on the whole approach. What
> changed between then and now? I can't detect any fundamental changes
> from the description.
>
This includes system oom handling alongside memcg oom handling. If you
have specific objections, please let us know, thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists