From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 25 Sep 2001 15:46:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 25 Sep 2001 15:46:16 -0400 Received: from [172.16.44.254] ([172.16.44.254]:44050 "EHLO int-mx1.corp.redhat.com") by vger.kernel.org with ESMTP id ; Tue, 25 Sep 2001 15:45:51 -0400 Date: Tue, 25 Sep 2001 14:46:11 -0500 From: Tommy Reynolds To: Pavel Machek Cc: linux-kernel@vger.kernel.org Subject: Re: GFP_FAIL? Message-Id: <20010925144611.01590a08.reynolds@redhat.com> In-Reply-To: <20010924210951.A165@bug.ucw.cz> In-Reply-To: <20010924210951.A165@bug.ucw.cz> Organization: Red Hat Software, Inc. / Embedded Development X-Mailer: Sylpheed version 0.6.2cvs5 (GTK+ 1.2.9; ) X-Face: Nr)Jjr was pleased to say: > Hi! > > I need to alloc as much memory as possible, *but not more*. I do not > want to OOM-kill anything. How do I do this? Tried GFP_KERNEL, will > oom-kill. GFP_USER will OOM-kill, too. Try GFP_ATOMIC; GFP_KERNEL sets the __GFP_WAIT flag and you don't want that. But, if you're really asking how to know how large the current working set is, so that you don't grab more than your applications are going to need and eventually OOM, you'll need to set GFP_HAVE_CRYSTAL_BALL ;-) -- Tommy Reynolds | Red Hat, Inc. (Embedded Development) | "The quickest way to do anything 307 Wynn Drive NW, Huntsville, AL 35805 USA | is right the first time." mailto:reynolds@redhat.com | - The Lieutenant (Rick Phone: +1.256.704.9286 | Jason), "Combat!", Mobile: +1.919.641.2923 | 1962 TV series FAX: +1.256.837.3839 |