[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240614181950.d5cd06acba24339401c98d6d@linux-foundation.org>
Date: Fri, 14 Jun 2024 18:19:50 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: kent.overstreet@...ux.dev, vbabka@...e.cz, pasha.tatashin@...een.com,
souravpanda@...gle.com, keescook@...omium.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] mm: handle profiling for fake memory allocations
during compaction
On Fri, 14 Jun 2024 16:05:04 -0700 Suren Baghdasaryan <surenb@...gle.com> wrote:
> During compaction isolated free pages are marked allocated so that they
> can be split and/or freed. For that, post_alloc_hook() is used inside
> split_map_pages() and release_free_list(). split_map_pages() marks free
> pages allocated, splits the pages and then lets alloc_contig_range_noprof()
> free those pages. release_free_list() marks free pages and immediately
> frees them. This usage of post_alloc_hook() affect memory allocation
> profiling because these functions might not be called from an instrumented
> allocator, therefore current->alloc_tag is NULL and when debugging is
> enabled (CONFIG_MEM_ALLOC_PROFILING_DEBUG=y) that causes warnings.
It would be helpful to quote the warnings for the changelog. And a
Reported-by:/Closes: if appropriate.
I'm assuming we want this in 6.10-rcX?
Please help in identifying the Fixes:, for anyone who might be
backporting allocation profiling.
Powered by blists - more mailing lists