From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12994 invoked by alias); 31 Oct 2011 15:19:30 -0000 Received: (qmail 12983 invoked by uid 22791); 31 Oct 2011 15:19:28 -0000 X-SWARE-Spam-Status: No, hits=-6.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 31 Oct 2011 15:19:10 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9VFJAX6030296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 31 Oct 2011 11:19:10 -0400 Received: from fche.csb (vpn-10-200.rdu.redhat.com [10.11.10.200]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p9VFJ9Oc001457; Mon, 31 Oct 2011 11:19:09 -0400 Received: by fche.csb (Postfix, from userid 2569) id 3CF325812C; Mon, 31 Oct 2011 11:19:09 -0400 (EDT) To: Mark Wielaard Cc: Josh Stone , systemtap@sourceware.org, dsmith@redhat.com Subject: Re: Fixed PR13146 by not allowing memory allocations to sleep References: <20110901143940.13672.qmail@sourceware.org> <1317135124.3361.22.camel@springer.wildebeest.org> <4E82481E.8060502@redhat.com> <1319545123.3228.24.camel@springer.wildebeest.org> <1320056765.3388.3.camel@springer.wildebeest.org> From: fche@redhat.com (Frank Ch. Eigler) Date: Mon, 31 Oct 2011 15:19:00 -0000 In-Reply-To: <1320056765.3388.3.camel@springer.wildebeest.org> (Mark Wielaard's message of "Mon, 31 Oct 2011 11:26:05 +0100") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2011-q4/txt/msg00126.txt.bz2 mjw wrote: > [...] >> I cannot find what precisely triggers/causes the oom-killer to kick in. >> I hoped a GFP_WILLING_TO_WAIT_BUT_DONT_KILL_ANYBODY_JUST_BECAUSE_OF_ME >> flag would exist, but it isn't clear to me which GFP flag/combination >> that actually corresponds to. > > Looking at the kernel sources it seems that flag is __GFP_NORETRY. > [...] We used to use __GFP_NORETRY for e.g. map allocation, since commit 132c23b4 some years ago. So I think this just swings our pendulum back to a previous point. - FChE