[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0904011226350.31960@chino.kir.corp.google.com>
Date: Wed, 1 Apr 2009 12:33:15 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Trilok Soni <soni.trilok@...il.com>
cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Greg KH <greg@...ah.com>, Paul Mundt <lethal@...ux-sh.org>,
Arve Hj?nnev?g <arve@...roid.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Pavel Machek <pavel@...e.cz>,
Brian Swetland <swetland@...gle.com>, arve@...gle.com,
San Mehat <san@...roid.com>, Robert Love <rlove@...gle.com>,
linux-kernel@...r.kernel.org,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
Tony Lindgren <tony@...mide.com>,
ext Juha Yrj?l? <juha.yrjola@...idboot.com>,
viktor.rosendahl@...ia.com
Subject: Re: lowmemory android driver not needed?
On Thu, 2 Apr 2009, Trilok Soni wrote:
> Any updates on top of mem_notify v6 patches? Is there any WIP for
> mem_notify with memcg infrastructure as you have pointed out above?
>
The /dev/mem_notify patches seem to have been abandoned, but there's still
an interest in a per-cgroup oom notifier. This shouldn't be restricted
only to the memory controller, however, since cpusets could use the
feature as well. Thus, it should probably be its own cgroup.
Implementing the same concept as /dev/mem_notify on top of the cgroup
interface would probably require some hacking to support such files, but
that support may not be far off anyway (devices that are only accessible
by an exclusive group of tasks).
--
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