From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0AA2CC43381 for ; Fri, 8 Mar 2019 07:42:29 +0000 (UTC) Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id BF8CE20811 for ; Fri, 8 Mar 2019 07:42:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=kroah.com header.i=@kroah.com header.b="FevCNOQX"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="NA6mTG+C" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BF8CE20811 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kroah.com Authentication-Results: mail.kernel.org; spf=fail smtp.mailfrom=kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.91) (envelope-from ) id 1h2A9D-0008Kw-LX for kernelnewbies@archiver.kernel.org; Fri, 08 Mar 2019 02:42:27 -0500 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by shelob.surriel.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1h2A7X-00065L-3s for kernelnewbies@kernelnewbies.org; Fri, 08 Mar 2019 02:40:43 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 3CE0E21C1B; Fri, 8 Mar 2019 02:40:41 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Fri, 08 Mar 2019 02:40:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=6Jdq7jgnrQZh5QTU+y+O1rR7Uqg s+yFa5EpznTesjAc=; b=FevCNOQXQ2XGNWga0zMfbQfwXD6A4rpWbqovdeDAb7G Kjzc/EuEXu69HBzMrnJhuk68w8UN3FWYLGhgzIoFJSEmxnCSkmziTEpHwp2i2jt9 kCtyAw3bgJWfkaXumRZpRMH9ctMpRkgKw95dyXV7hWMTKZLrXu/JQG6OrZC4+Xnz 1p4Y2K0HrFw45ytR+gF+1k5UjyVSGHtOdIhGttMd1rlLaMQMDvana1GffS059NqT P2oEGNAVNiKXHI/YNWX958FcKS89XRYviegQr8TF02K0wswoiNwknjb5jKMMbABN 119yZ3qzM883RMSxMJt/A7hF+sgTYSd2FkuGoU/8BqQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=6Jdq7j gnrQZh5QTU+y+O1rR7Uqgs+yFa5EpznTesjAc=; b=NA6mTG+CyKDHQYEE83PuID SLaN6JjpBwOLCQglFiUBPpWETVCYtbetBwW9lHzLAjbmBq45sKDOypy/BjKs5DDF SKH+AwJwg1YoNFFdcixcJXsP0ralOAJ8FxTHKroHxhWFyh2tpEc3lVmM5R4Idiqy /y952FjVko7VQEUL6jqF4AttWlTie0Hj8NDvW1kjxTZgP0LsRY3s/k9A2OqCe/CT Lr/q5HAwY8KapNo8mghXIgq7Dq4crGoupKjGfXYWdKCxh0hbuzyGd1fSHSHLf5Hq Z4CoWhF8Om6n8ZU75iQzzqgE/1vqPnrNXlq+3zn4sfHQuixWXCPuf3RtA4+vQzxg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrfeelgddutdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujggfsehttd ertddtredvnecuhfhrohhmpehgrhgvghcukhhhuceoghhrvghgsehkrhhorghhrdgtohhm qeenucfkphepkeefrdekiedrkeelrddutdejnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hgrhgvgheskhhrohgrhhdrtghomhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from localhost (5356596b.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id 7D87EE4546; Fri, 8 Mar 2019 02:40:37 -0500 (EST) Date: Fri, 8 Mar 2019 08:40:36 +0100 From: greg kh To: wuzhouhui Subject: Re: Re: How to avoid or reduce GFP_ATOMIC allocation failed Message-ID: <20190308074035.GA16279@kroah.com> References: <51af9230.9ed2.1695bce6545.Coremail.wuzhouhui14@mails.ucas.ac.cn> <20190308072152.GA10654@kroah.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.3 (2019-02-01) Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces+kernelnewbies=archiver.kernel.org@kernelnewbies.org On Fri, Mar 08, 2019 at 03:34:18PM +0800, wuzhouhui wrote: > > -----Original Messages----- > > From: "Greg KH" > > Sent Time: 2019-03-08 15:21:52 (Friday) > > To: wuzhouhui > > Cc: kernelnewbies@kernelnewbies.org > > Subject: Re: How to avoid or reduce GFP_ATOMIC allocation failed > > > > On Fri, Mar 08, 2019 at 01:37:26PM +0800, wuzhouhui wrote: > > > Hi, > > > > > > I check kernel code and found that GFP_ATOMIC allocation will > > > use emergency pool and maybe failed if emergency pool is not > > > enough. And GFP_ATOMIC doesn't trigger reclaim (because of > > > ATOMIC) even if there are a lot of page caches. So my question > > > is how to avoid or reduce GFP_ATOMIC allocation failed if there > > > are enough reclaimable memory? Is there some kernel parameters > > > can be configured? > > > > Have you seen the ATOMIC pools be used up and not able to be reclaimed > > in real-world usages? If so, I'm sure the mm developers would love to > > No, I haven't seen this scenario. But I encountered the similar issue > with [1] (order is 5 in my scenario), and this issue is not resolved for > now. Please work with the company that created your out-of-tree kernel networking code as it sounds like they do not know how to properly handle this type of problem :) good luck! greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies