[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <58d4f340549dd69a5d605c1526ceceb035b3cc98@linux.dev>
Date: Thu, 09 Nov 2023 16:04:39 +0000
From: jeff.xie@...ux.dev
To: "Matthew Wilcox" <willy@...radead.org>,
"Jeff Xie" <xiehuan09@...il.com>
Cc: akpm@...ux-foundation.org, iamjoonsoo.kim@....com, vbabka@...e.cz,
cl@...ux.com, penberg@...nel.org, rientjes@...gle.com,
roman.gushchin@...ux.dev, 42.hyeyoo@...il.com, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
chensong_2000@....cn
Subject: Re: [RFC][PATCH 1/4] mm, page_owner: add folio allocate post callback
for struct page_owner to make the owner clearer
November 9, 2023 at 11:36 PM, "Matthew Wilcox" <willy@...radead.org> wrote:
>
> On Thu, Nov 09, 2023 at 11:25:18PM +0800, Jeff Xie wrote:
>
> >
> > From the perspective of a folio, it cannot obtain information about
> > all the situations in which folios are allocated.
> > If we want to determine whether a folio is related to vmalloc or
> > kernel_stack or the other memory allocation process,
> > using just a folio parameter is not sufficient. To achieve this goal,
> > we can add a callback function to provide more extensibility and
> > information.
> >
>
> But we want that anyway (or at least I do). You're right that vmalloc
> pages are not marked as being vmalloc pages and don't contain the
> information about which vmalloc area they belong to. I've talked about
> ways we can add that information to folios in the past, but I have a lot
> of other projects I'm working on. Are you interested in doing that?
>
Certainly, I'm willing to give it a try. If a folio can include vmalloc information
or more information, this is great. I may need to understand the background of why
you proposed this method in the past.
--
Jeff Xie
Powered by blists - more mailing lists