November 9, 2023 at 11:36 PM, "Matthew Wilcox" <willy@xxxxxxxxxxxxx> 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
