[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220811082132.GA17685@lst.de>
Date: Thu, 11 Aug 2022 10:21:32 +0200
From: Christoph Hellwig <hch@....de>
To: Michal Hocko <mhocko@...e.com>
Cc: Christoph Hellwig <hch@....de>,
Andrew Morton <akpm@...ux-foundation.org>,
Baoquan He <bhe@...hat.com>,
John Donnelly <john.p.donnelly@...cle.com>,
David Hildenbrand <david@...hat.com>, linux-mm@...ck.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] dma/pool: do not complain if DMA pool is not allocated
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.
Powered by blists - more mailing lists