From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx172.postini.com [74.125.245.172]) by kanga.kvack.org (Postfix) with SMTP id 0F8F76B0062 for ; Wed, 31 Oct 2012 14:45:08 -0400 (EDT) Received: by mail-pa0-f41.google.com with SMTP id fa10so1296811pad.14 for ; Wed, 31 Oct 2012 11:45:07 -0700 (PDT) Date: Wed, 31 Oct 2012 11:45:04 -0700 (PDT) From: David Rientjes Subject: Re: zram OOM behavior In-Reply-To: Message-ID: References: <20121015144412.GA2173@barrios> <20121022235321.GK13817@bbox> <20121030001809.GL15767@bbox> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: Luigi Semenzato Cc: Minchan Kim , linux-mm@kvack.org, Dan Magenheimer , KOSAKI Motohiro , Sonny Rao On Tue, 30 Oct 2012, Luigi Semenzato wrote: > To make it clear, I am suggesting that this "fix" might work as a > temporary workaround until a better fix is available. > A temporary workaround is to do a kill -9 of the hung process since even the 3.4 oom killer will automatically give it access to memory reserves. -- 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