From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756612AbZEDOZK (ORCPT ); Mon, 4 May 2009 10:25:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754094AbZEDOY5 (ORCPT ); Mon, 4 May 2009 10:24:57 -0400 Received: from smtp.ultrahosting.com ([74.213.174.254]:47876 "EHLO smtp.ultrahosting.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753831AbZEDOY5 (ORCPT ); Mon, 4 May 2009 10:24:57 -0400 Date: Mon, 4 May 2009 10:13:34 -0400 (EDT) From: Christoph Lameter X-X-Sender: cl@qirst.com To: Cyrill Gorcunov cc: Ingo Molnar , Andrew Morton , Mel Gorman , LKML , Pekka Enberg , Rik van Riel , David Rientjes , Pavel Emelyanov Subject: Re: [PATCH -tip] mm: introduce __GFP_PANIC modifier In-Reply-To: <20090504141256.GK4173@lenovo> Message-ID: References: <20090504122740.GH4173@lenovo> <20090504131311.GA23330@elte.hu> <20090504131638.GJ4173@lenovo> <20090504141256.GK4173@lenovo> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 4 May 2009, Cyrill Gorcunov wrote: > As I see page allocator already quite modified in -mm tree. > Christoph will kmalloc with (__GFP_NOFAIL | __GFP_REPEAT) > inform us on exhausted memory? Or we just stuck with blank > screen instead (not blank actually but with previous messages)? If you do not specify __GFP_NOWARN then it should give you messages, Guess we need to very that it behaves in the right wya.