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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5D8D8C19F2D for ; Thu, 11 Aug 2022 08:21:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234284AbiHKIVk (ORCPT ); Thu, 11 Aug 2022 04:21:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56700 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234386AbiHKIVh (ORCPT ); Thu, 11 Aug 2022 04:21:37 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C8ACB4B0E4 for ; Thu, 11 Aug 2022 01:21:36 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id D889F68AA6; Thu, 11 Aug 2022 10:21:32 +0200 (CEST) Date: Thu, 11 Aug 2022 10:21:32 +0200 From: Christoph Hellwig To: Michal Hocko Cc: Christoph Hellwig , Andrew Morton , Baoquan He , John Donnelly , David Hildenbrand , linux-mm@kvack.org, LKML Subject: Re: [PATCH] dma/pool: do not complain if DMA pool is not allocated Message-ID: <20220811082132.GA17685@lst.de> References: <20220325122559.14251-1-mhocko@kernel.org> <20220325164856.GA16800@lst.de> <20220811072817.GB13886@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 11, 2022 at 10:20:43AM +0200, Michal Hocko wrote: > Meminfo part says > Node 0 DMA free:160kB boost:0kB min:0kB low:0kB high:0kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15996kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB > > So the zone has 15MB of managed memory (by the page allocator), yet only > 160kB is free early boot during the allocation. So it is mostly consumed > by somebody. I haven't really checked by whom. > > Does that exaplain the above better? Yes. I'm really curious who eats up all the GFP_DMA memory early during boot, though.