From: "Arve Hjønnevåg" <arve@android.com>
To: "Greg KH" <greg@kroah.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Pavel Machek" <pavel@suse.cz>,
"Brian Swetland" <swetland@google.com>,
arve@google.com, "San Mehat" <san@android.com>,
"Robert Love" <rlove@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: lowmemory android driver not needed?
Date: Wed, 14 Jan 2009 15:32:38 -0800 [thread overview]
Message-ID: <d6200be20901141532y6f236104kd521041d640c152e@mail.gmail.com> (raw)
In-Reply-To: <20090114231739.GB24111@kroah.com>
On Wed, Jan 14, 2009 at 3:17 PM, Greg KH <greg@kroah.com> wrote:
>> We actually use 6 different thresholds for killing processes. I don't
>> know what all the classes are, processes with a higher oom_adj value
>> can be killed with less impact to the user than processes with a lower
>> oom_adj value. The first few classes only affect latency when
>> switching apps, but later classes stop non critical background
>> services and finally the foreground app. Another reason to not kill
>> every process at the same threshold is that memory may not be free
>> immediately when the process is killed.
>
> But the lowmemorykiller android module doesn't have anything to do with
> this, right?
>
It does. We write the thresholds to
/sys/module/lowmemorykiller/parameters/adj and
/sys/module/lowmemorykiller/parameters/minfree then set the oom_adj
value per process. If the standard oom killer can be adjusted in a
similar way, then we will not need the lowmemorykiller module.
--
Arve Hjønnevåg
next prev parent reply other threads:[~2009-01-14 23:32 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 [this message]
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
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=d6200be20901141532y6f236104kd521041d640c152e@mail.gmail.com \
--to=arve@android.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arve@google.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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®