From: David Rientjes <rientjes@google.com>
To: "Arve Hjønnevåg" <arve@android.com>
Cc: John Stultz <john.stultz@linaro.org>,
lkml <linux-kernel@vger.kernel.org>,
Android Kernel Team <kernel-team@android.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 1/5] staging: android: lowmemorykiller: Add config option to support oom_adj values
Date: Wed, 27 Feb 2013 16:14:12 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1302271613210.27317@chino.kir.corp.google.com> (raw)
In-Reply-To: <CAMP5XgemB4AdKEY4HFLwupo1CGv89hbmB+HUYYN8qdQRYCTdHg@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 411 bytes --]
On Wed, 27 Feb 2013, Arve Hjønnevåg wrote:
> Because, without this patch, the values written to
> /sys/module/lowmemorykiller/parameters/adj do not get adjusted and
> therefore do not match the correct processes.
>
Explain how this can possibly be consistent if your system includes two
processes, one writing oom_adj values and one writing oom_score_adj
values, and the kernel has this new option enabled?
next prev parent reply other threads:[~2013-02-28 0:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 6:07 [PATCH 0/5] staging: Updates from the Android tree (for 3.10) John Stultz
2013-02-27 6:07 ` [PATCH 1/5] staging: android: lowmemorykiller: Add config option to support oom_adj values John Stultz
2013-02-27 22:18 ` David Rientjes
2013-02-27 22:38 ` Arve Hjønnevåg
2013-02-27 23:12 ` David Rientjes
2013-02-27 23:47 ` Arve Hjønnevåg
2013-02-28 0:14 ` David Rientjes [this message]
2013-02-28 1:05 ` Arve Hjønnevåg
2013-02-28 1:41 ` David Rientjes
2013-02-27 6:07 ` [PATCH 2/5] staging: android: lowmemorykiller: Don't count reserved free memory John Stultz
2013-02-27 22:19 ` David Rientjes
2013-02-27 6:07 ` [PATCH 3/5] staging: android: lowmemorykiller: Change default debug_level to 1 John Stultz
2013-02-27 6:07 ` [PATCH 4/5] staging: android: logger: Allow a UID to read it's own log entries John Stultz
2013-02-27 6:07 ` [PATCH 5/5] staging: android: logger: enforce GID and CAP check on log flush John Stultz
2013-03-05 8:39 ` [PATCH 0/5] staging: Updates from the Android tree (for 3.10) Greg Kroah-Hartman
2013-03-05 9:56 ` John Stultz
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=alpine.DEB.2.02.1302271613210.27317@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=arve@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).