[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0905071147260.26631@chino.kir.corp.google.com>
Date: Thu, 7 May 2009 11:50:04 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Andrew Morton <akpm@...ux-foundation.org>, 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 Thu, 7 May 2009, Rafael J. Wysocki wrote:
> Unfortunately it fails too quickly with the combination as well, so it looks
> like we can't use __GFP_NORETRY during hibernation.
>
If you know that no other tasks are in the oom killer at suspend time, you
can do what I mentioned earlier:
struct zone *z;
for_each_populated_zone(z)
zone_set_flag(z, ZONE_OOM_LOCKED);
and then later
for_each_populated_zone(z)
zone_clear_flag(z, ZONE_OOM_LOCKED);
The only race there is if a task is currently in the oom killer and will
subsequently clear ZONE_OOM_LOCKED for its zonelist.
--
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