From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx105.postini.com [74.125.245.105]) by kanga.kvack.org (Postfix) with SMTP id BE1736B00AA for ; Thu, 1 Nov 2012 17:48:06 -0400 (EDT) Received: by mail-pa0-f41.google.com with SMTP id fa10so2225800pad.14 for ; Thu, 01 Nov 2012 14:48:06 -0700 (PDT) Date: Thu, 1 Nov 2012 14:48:03 -0700 (PDT) From: David Rientjes Subject: Re: zram OOM behavior In-Reply-To: Message-ID: References: <20121030001809.GL15767@bbox> <20121031005738.GM15767@bbox> <20121101024316.GB24883@bbox> <20121101082814.GL3888@suse.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: Luigi Semenzato Cc: Mel Gorman , Minchan Kim , linux-mm@kvack.org, Dan Magenheimer , KOSAKI Motohiro , Sonny Rao On Thu, 1 Nov 2012, Luigi Semenzato wrote: > So which one should I try first, David's change or Mel's? > > Does Mel's change take into account the fact that the exiting process > is already deep into do_exit() (exit_mm() to be precise) when it tries > to allocate? > Mel's patch is addressing a separate issue since you've already proven that your problem is calling the oom killer which wouldn't occur if your thread had SIGKILL prior to Mel's patch. It would allow my suggested workaround of killing the hung task to end the livelock, though, but that shouldn't be needed after my patch. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org