From: "MinChan Kim" <minchan.kim@gmail.com>
To: "Arve Hjønnevåg" <arve@android.com>,
"Balbir Singh" <balbir@linux.vnet.ibm.com>,
"KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Rik van Riel" <riel@surriel.com>, linux-mm <linux-mm@kvack.org>
Cc: "Brian Swetland" <swetland@google.com>,
"Greg KH" <greg@kroah.com>,
arve@google.com, "San Mehat" <san@android.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Robert Love" <rlove@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: lowmemory android driver not needed?
Date: Wed, 14 Jan 2009 15:45:35 +0900 [thread overview]
Message-ID: <28c262360901132245j8fe121naf1d6b1450b4cade@mail.gmail.com> (raw)
In-Reply-To: <d6200be20901131830r7103ff8eoe0314f9faf89d89b@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 2513 bytes --]
Hi, Arve.
On Wed, Jan 14, 2009 at 11:30 AM, Arve Hjønnevåg <arve@android.com> wrote:> The oom killer does not kick in until all caches are emptied. Our user> space code changes the oom_adj value of processes that are no longer> in the foreground so that they killed first (the process saves its> state but does not exit). To avoid excessive demand paging, the low> memory killer will kill these processes when the memory available> drops below a threshold.
It have some problems. (drivers/staging/android/lwmemorykiller.c)
1. lowmem_shrink function have to answer about vm's query the cache size fast.2. it don't consider page size and memory size when it makelowmem_minfree's values.3. If system have many processes, for_each_process take a long time.it may result system latency although lowmemkiller intend to avoidlatency.4. Most important thing. Could we use memory controller instead oflowmemkiller ? I am not sure since I don't follow up memory controllerin these days.
I think we have to use existing facility if possible.Previously, There are similar kinds of patches. but It can't mergemainline due to some issue. They can comment about lowmemkiller. Iwill CC them.
> --> Arve Hjønnevåg>>> On Tue, Jan 13, 2009 at 6:18 PM, Brian Swetland <swetland@google.com> wrote:>>>> Looping in Arve who wrote the low memory killer and can explain things>> in more detail.>>>> Brian>>>> [Greg KH <greg@kroah.com>]>>> Hi San,>>>>>> Alan Cox pointed me at the /proc/<pid>/oom_adj file that controls the>>> oom-killer score for any process as being more than sufficent to control>>> the oom killer.>>>>>> This makes me wonder why you wrote the android lowmemlorykiller driver?>>>>>> What is that driver for that is not already present in the existing>>> oom_* values for every process?>>>>>> thanks,>>>>>> greg k-h>> -->> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in>> the body of a message to majordomo@vger.kernel.org>> More majordomo info at http://vger.kernel.org/majordomo-info.html>> Please read the FAQ at http://www.tux.org/lkml/>>> --> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in> the body of a message to majordomo@vger.kernel.org> More majordomo info at http://vger.kernel.org/majordomo-info.html> Please read the FAQ at http://www.tux.org/lkml/>
-- Kinds regards,MinChan Kimÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2009-01-14 6:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 1:02 Greg KH
2009-01-14 2:18 ` Brian Swetland
2009-01-14 2:30 ` Arve Hjønnevåg
2009-01-14 3:52 ` Greg KH
2009-01-14 10:43 ` Pavel Machek
2009-01-14 10:48 ` Alan Cox
2009-01-14 12:18 ` MinChan Kim
2009-01-14 22:26 ` Arve Hjønnevåg
2009-01-14 23:17 ` Greg KH
2009-01-14 23:32 ` Arve Hjønnevåg
2009-01-15 0:12 ` Greg KH
2009-01-15 0:54 ` [PATCH] Staging: android: Add lowmemorykiller documentation Arve Hjønnevåg
2009-01-15 0:59 ` Greg KH
2009-01-15 13:32 ` lowmemory android driver not needed? Trilok Soni
2009-01-15 23:44 ` Greg KH
2009-01-16 9:02 ` Paul Mundt
2009-01-16 11:16 ` KOSAKI Motohiro
2009-01-16 15:23 ` Greg KH
2009-01-21 2:50 ` KOSAKI Motohiro
2009-01-21 3:05 ` Paul Mundt
2009-01-21 3:29 ` KAMEZAWA Hiroyuki
2009-04-01 18:38 ` Trilok Soni
2009-04-01 19:33 ` David Rientjes
2009-02-03 20:55 ` Tony Lindgren
2009-01-16 11:42 ` KOSAKI Motohiro
2009-01-16 13:18 ` KOSAKI Motohiro
2009-01-22 6:13 ` Arve Hjønnevåg
2009-01-29 1:48 ` KOSAKI Motohiro
2009-01-29 2:51 ` Arve Hjønnevåg
2009-01-29 3:45 ` KAMEZAWA Hiroyuki
2009-01-29 4:27 ` Greg KH
2009-01-29 4:43 ` KOSAKI Motohiro
2009-01-29 4:59 ` Greg KH
2009-01-29 5:29 ` KOSAKI Motohiro
2009-01-30 6:20 ` Greg KH
2009-01-30 6:41 ` Brian Swetland
2009-02-03 13:40 ` KOSAKI Motohiro
2009-01-29 22:06 ` Pavel Machek
2009-02-03 14:08 ` KOSAKI Motohiro
2009-01-15 7:55 ` David Rientjes
2009-01-14 6:45 ` MinChan Kim [this message]
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=28c262360901132245j8fe121naf1d6b1450b4cade@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arve@android.com \
--cc=arve@google.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=greg@kroah.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=rlove@google.com \
--cc=san@android.com \
--cc=swetland@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
all inboxes | Powered by JetHome®