[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090507153824.df54658c.akpm@linux-foundation.org>
Date: Thu, 7 May 2009 15:38:24 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: rientjes@...gle.com, fengguang.wu@...el.com,
linux-pm@...ts.linux-foundation.org, pavel@....cz,
torvalds@...ux-foundation.org, jens.axboe@...cle.com,
alan-jenkins@...fmail.co.uk, linux-kernel@...r.kernel.org,
kernel-testers@...r.kernel.org
Subject: Re: [PATCH 1/5] mm: Add __GFP_NO_OOM_KILL flag
On Fri, 8 May 2009 00:14:48 +0200
"Rafael J. Wysocki" <rjw@...k.pl> wrote:
> IOW, you need to freeze the user space totally before trying to disable the
> OOM killer.
Not necessarily. We only need to take action if a task is about to
start oom-killing - presumably by taking a nap.
If a process is sitting there happily computing pi then we can leave it
running.
--
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