[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84FF21A720B0874AA94B46D76DB98269045545E5@008-AM1MPN1-003.mgdnok.nokia.com>
Date: Thu, 5 Jan 2012 16:13:27 +0000
From: <leonid.moiseichuk@...ia.com>
To: <gregkh@...e.de>
CC: <penberg@...nel.org>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>, <cesarb@...arb.net>,
<kamezawa.hiroyu@...fujitsu.com>, <emunson@...bm.net>,
<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
-----Original Message-----
From: ext Greg KH [mailto:gregkh@...e.de]
>No, please listen to what people, including me, are saying, otherwise your code will be totally ignored.
I tried to sort out all inputs coming. But before doing the next step I prefer to have tests passed. Changes you proposed are strain forward and understandable.
Hooking in mm/vmscan.c and mm/page-writeback.c is not so easy, I need to find proper place and make adequate proposal.
Using memcg is doesn't not look for me now as a good way because I wouldn't like to change memory accounting - memcg has strong reason to keep caches.
Best Wishes,
Leonid
--
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