From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx126.postini.com [74.125.245.126]) by kanga.kvack.org (Postfix) with SMTP id ABA4B6B004F for ; Fri, 13 Jan 2012 06:51:52 -0500 (EST) From: Subject: RE: [PATCH 3.2.0-rc1 3/3] Used Memory Meter pseudo-device module Date: Fri, 13 Jan 2012 11:51:02 +0000 Message-ID: <84FF21A720B0874AA94B46D76DB982690455759C@008-AM1MPN1-003.mgdnok.nokia.com> References: <20120104195521.GA19181@suse.de> <84FF21A720B0874AA94B46D76DB9826904554AFD@008-AM1MPN1-003.mgdnok.nokia.com> <84FF21A720B0874AA94B46D76DB9826904554B81@008-AM1MPN1-003.mgdnok.nokia.com> <84FF21A720B0874AA94B46D76DB98269045568A1@008-AM1MPN1-003.mgdnok.nokia.com> <84FF21A720B0874AA94B46D76DB9826904556CB7@008-AM1MPN1-003.mgdnok.nokia.com> <84FF21A720B0874AA94B46D76DB9826904557417@008-AM1MPN1-003.mgdnok.nokia.com> In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: owner-linux-mm@kvack.org List-ID: To: rientjes@google.com Cc: gregkh@suse.de, linux-mm@kvack.org, linux-kernel@vger.kernel.org, cesarb@cesarb.net, kamezawa.hiroyu@jp.fujitsu.com, emunson@mgebm.net, penberg@kernel.org, aarcange@redhat.com, riel@redhat.com, mel@csn.ul.ie, dima@android.com, rebecca@android.com, san@google.com, akpm@linux-foundation.org, vesa.jaaskelainen@nokia.com > -----Original Message----- > From: ext David Rientjes [mailto:rientjes@google.com] > Sent: 13 January, 2012 12:06 > To: Moiseichuk Leonid (Nokia-MP/Helsinki) ... > > Why? That is expected that product tested and tuned properly, > > applications fixed, and at least no apps installed which might consume > > 100 MB in second or two. >=20 > I'm trying to make this easy for you, if you haven't noticed. Thanks, I did. > Your memory threshold, as proposed, will have values that are tied direct= ly to the > implementation of the VM in the kernel when its under memory pressure > and that implementation evolves at a constant rate. Not sure that I understand this statement. Free/Used/Active page sets are p= roperties of any VM. I have a new implementation but it is in testing now. I do not see any rela= tion to VM implementation except statistics and it could be extended with=20 "virtual values" which are suitable for user-space e.g. active page set. It= could be extended with something else if someone needs it.=20 The thresholds are set by user-space and individual for applications which= likes to be informed. > mlock() the memory that your userspace monitoring needs to send signals t= o > applications, whether those signals are handled to free memory internally= or > its SIGTERM or SIGKILL. Mlocked memory should be avoid as much as possible because efficiency rate = is lowest possible and makes situation for non-mlocked pages even worse. You cannot mlock whole UI only most critical parts. Thus, handling time in case of 3rd party apps will be not controllable, Use= r will observe it as device jam/hang/freeze.=20 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org