[<prev] [next>] [day] [month] [year] [list]
Message-Id: <E1PHQ64-0001M1-OD@be1.7eggert.dyndns.org>
Date: Sun, 14 Nov 2010 01:05:28 +0100
From: Bodo Eggert <7eggert@....de>
To: Mandeep Singh Baines <msb@...gle.com>,
David Rientjes <rientjes@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Rik van Riel <riel@...hat.com>,
Ying Han <yinghan@...gle.com>, linux-kernel@...r.kernel.org,
gspencer@...omium.org, piman@...omium.org, wad@...omium.org,
olofj@...omium.org, Bodo Eggert <7eggert@....de>
Subject: Re: [PATCH] oom: allow a non-CAP_SYS_RESOURCE proces to oom_score_adj down
Mandeep Singh Baines <msb@...gle.com> wrote:
> We'd like to be able to oom_score_adj a process up/down as its
> enters/leaves the foreground. Currently, it is not possible to oom_adj
> down without CAP_SYS_RESOURCE. This patch allows a task to decrease
> its oom_score_adj back to the value that a CAP_SYS_RESOURCE thread set
> it or its inherited value at fork. Assuming the thread that has forked
> it has oom_score_adj of 0, each tab
process
> could decrease it back from 0 upon
> activation unless a CAP_SYS_RESOURCE thread elevated it to something
> higher.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists