Re: [RFC][PATCH 1/4] mm, page_owner: add folio allocate post callback for struct page_owner to make the owner clearer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [NTFS 3]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [NTFS 3]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux