linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: <leonid.moiseichuk@nokia.com>
To: minchan@kernel.org, anton.vorontsov@linaro.org
Cc: kosaki.motohiro@gmail.com, riel@redhat.com, penberg@kernel.org,
	john.stultz@linaro.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org,
	patches@linaro.org, kernel-team@android.com,
	glommer@parallels.com, kamezawa.hiroyu@jp.fujitsu.com,
	suleiman@google.com
Subject: RE: [PATCH v4] vmevent: Implement greater-than attribute state and one-shot mode
Date: Wed, 2 May 2012 06:46:15 +0000	[thread overview]
Message-ID: <84FF21A720B0874AA94B46D76DB98269045D2AC9@008-AM1MPN1-003.mgdnok.nokia.com> (raw)
In-Reply-To: <4FA0C042.9010907@kernel.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1333 bytes --]

> -----Original Message-----
> From: ext Minchan Kim [mailto:minchan@kernel.org]
> Sent: 02 May, 2012 08:04
> To: Anton Vorontsov
> Cc: KOSAKI Motohiro; Rik van Riel; Pekka Enberg; Moiseichuk Leonid (Nokia-
...
> I think hardest problem in low mem notification is how to define _lowmem
> situation_.
> We all guys (server, desktop and embedded) should reach a conclusion on
> define lowmem situation before progressing further implementation
> because each part can require different limits.
> Hopefully, I want it.
> 
> What is the best situation we can call it as "low memory"?

That depends on what user-space can do. In n9 case [1] we can handle some OOM/slowness-prevention and actions e.g. close background applications, stop prestarted apps, 
flush browser/graphics caches in applications and do all the things kernel even don't know about. This set of activities usually comes as memory management design.

From another side, polling by re-scan vmstat data using procfs might be performance heavy and for sure - use-time disaster.

Leonid
[1] http://maemo.gitorious.org/maemo-tools/libmemnotify - yes, not ideal but it works and quite well isolated code.
N‹§²æìr¸›zǧu©ž²Æ {\b­†éì¹»\x1c®&Þ–)îÆi¢žØ^n‡r¶‰šŽŠÝ¢j$½§$¢¸\x05¢¹¨­è§~Š'.)îÄÃ,yèm¶ŸÿÃ\f%Š{±šj+ƒñb‚^[nö¢®×¥yÊ&Š{^®w­r\x16«ë"œ&§iÖ¬Š	á¶Ú\x7fþËh¦Ø^™ë^­Æ¿\x0e‰ízf¢•¨ky

  reply	other threads:[~2012-05-02  6:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18  8:32 [PATCH v2 0/2] vmevent: Greater-than attribute + one-shot mode + a bugfix Anton Vorontsov
2012-04-18  8:33 ` [PATCH 1/2] vmevent: Should not grab mutex in the atomic context Anton Vorontsov
2012-04-18 20:01   ` Pekka Enberg
2012-04-18  8:35 ` [PATCH 2/2] vmevent: Implement greater-than attribute and one-shot mode Anton Vorontsov
2012-04-18 20:01   ` Pekka Enberg
2012-04-18 22:46     ` Anton Vorontsov
2012-04-19  5:42       ` Pekka Enberg
2012-04-19 16:29         ` [PATCH v3 " Anton Vorontsov
2012-05-01 13:18           ` [PATCH v4] vmevent: Implement greater-than attribute state " Anton Vorontsov
2012-05-01 21:04             ` Rik van Riel
2012-05-02  0:20               ` Anton Vorontsov
2012-05-02  1:20                 ` KOSAKI Motohiro
2012-05-02  3:31                   ` Anton Vorontsov
2012-05-02  3:50                     ` Anton Vorontsov
2012-05-02  5:04                     ` Minchan Kim
2012-05-02  6:46                       ` leonid.moiseichuk [this message]
2012-05-02  6:57                       ` Pekka Enberg
2012-05-02  7:41                         ` Minchan Kim
2012-05-02  6:51                   ` Pekka Enberg
2012-05-03 10:52             ` Pekka Enberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84FF21A720B0874AA94B46D76DB98269045D2AC9@008-AM1MPN1-003.mgdnok.nokia.com \
    --to=leonid.moiseichuk@nokia.com \
    --cc=anton.vorontsov@linaro.org \
    --cc=glommer@parallels.com \
    --cc=john.stultz@linaro.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kernel-team@android.com \
    --cc=kosaki.motohiro@gmail.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=patches@linaro.org \
    --cc=penberg@kernel.org \
    --cc=riel@redhat.com \
    --cc=suleiman@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox