[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F063FC0.8000907@gmail.com>
Date: Thu, 05 Jan 2012 19:26:40 -0500
From: KOSAKI Motohiro <kosaki.motohiro@...il.com>
To: leonid.moiseichuk@...ia.com
CC: kosaki.motohiro@...il.com, gregkh@...e.de, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, cesarb@...arb.net,
kamezawa.hiroyu@...fujitsu.com, emunson@...bm.net,
penberg@...nel.org, aarcange@...hat.com, riel@...hat.com,
mel@....ul.ie, rientjes@...gle.com, dima@...roid.com,
rebecca@...roid.com, san@...gle.com, akpm@...ux-foundation.org,
vesa.jaaskelainen@...ia.com
Subject: Re: [PATCH 3.2.0-rc1 0/3] Used Memory Meter pseudo-device and related
changes in MM
> Android OOM (AOOM) is a different thing. Briefly Android OOM is a safety belt,
>but I try to introduce look-ahead radar to stop before hitting wall.
You explained why we shouldn't merge neither you nor android notification patches.
Many embedded developers tried to merge their own patch and claimed "Hey! my patch
is completely different from another one". That said, their patches can't be used
each other use case, just for them.
Systemwide global notification itself is not bad idea. But we definitely choose
just one implementation. thus, you need to get agree with other embedded people.
Again, lowmemorykiller.c should be dropped too.
> UsedMemory = (MemTotal - MemFree - Buffers - Cached - SwapCached) +
> (SwapTotal - SwapFree)
If you spent a few time to read past discuttion, you should have understand your fomula
is broken and unacceptable. Think, mlocked (or pinning by other way) cache can't be
discarded. And, When system is under swap thrashing, userland notification is
useless. I don't think you tested w/ swap environment heavily.
While you are getting stuck to make nokia specific feature, I'm recommending you
maintain your local patch yourself.
--
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