From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Schmidt Subject: Re: [PATCH] bnx2x: avoid atomic allocations during initialization Date: Mon, 09 Sep 2013 14:20:03 +0200 Message-ID: <522DBCF3.50709@redhat.com> References: <1378411989-19775-1-git-send-email-mschmidt@redhat.com> <20130906.142735.458916282873797040.davem@davemloft.net> <504C9EFCA2D0054393414C9CB605C37F20D90E3D@SJEXCHMB06.corp.ad.broadcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: David Miller , "netdev@vger.kernel.org" , Ariel Elior , Eilon Greenstein To: Dmitry Kravkov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:54467 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751960Ab3IIMUN (ORCPT ); Mon, 9 Sep 2013 08:20:13 -0400 In-Reply-To: <504C9EFCA2D0054393414C9CB605C37F20D90E3D@SJEXCHMB06.corp.ad.broadcom.com> Sender: netdev-owner@vger.kernel.org List-ID: On 09/07/2013 03:45 AM, Dmitry Kravkov wrote: > Once you allocated the memory during initialization , you will most > probably fail to allocate its replacement during RX handling (on this > machine). Why do you think this would happen "most probably"? I would instead expect the VM subsystem to respond to the memory pressure created by the initial GFP_KERNEL allocations by freeing some memory to allow the future atomic allocations to succeed. Michal