From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id D9C0DC4167D
	for <linux-kernel@archiver.kernel.org>; Thu,  9 Nov 2023 15:37:07 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1343506AbjKIPhI (ORCPT
        <rfc822;linux-kernel@archiver.kernel.org>);
        Thu, 9 Nov 2023 10:37:08 -0500
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34460 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S229770AbjKIPhF (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 9 Nov 2023 10:37:05 -0500
Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 28B061FF3;
        Thu,  9 Nov 2023 07:37:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
        d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version:
        References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:
        Content-Transfer-Encoding:Content-ID:Content-Description;
        bh=NFkxRWLuyVaV5/yNfiI+b9FYk59N9eHUD1UJ8k1Z614=; b=C0nU4zM0T0T6q/7Qvr8X7IG/y3
        OkPoel1ipzsmpCRIxUDl6YpjY3bCAU06orKheElFPV+a6RT5JaI5YDAHjxMacFYzAs504gfxFcRRA
        mmWpexVWorumSWIXjTmiqUh/SSpYnObfImSbEzqthgXmZDFBjaoegrH+8nSxjOpfLXZ18K0qzFhFu
        z8hdk3zsKGbxybdxwvj98hBhYE8rziJu+5II3xY/LpwfxtbU2i882ubzBF0N1vB9a6VZkO8plQStE
        L+F8kQA0fRD/z4JLgELMaNap5hmobTKe74W5iWLFCAATx6gsTyGIoIYImv+H5dJIg47S3njqr0y6J
        jrMKzUGQ==;
Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux))
        id 1r175N-0082n4-PC; Thu, 09 Nov 2023 15:36:49 +0000
Date:   Thu, 9 Nov 2023 15:36:49 +0000
From:   Matthew Wilcox <willy@infradead.org>
To:     Jeff Xie <xiehuan09@gmail.com>
Cc:     Jeff Xie <jeff.xie@linux.dev>, akpm@linux-foundation.org,
        iamjoonsoo.kim@lge.com, vbabka@suse.cz, cl@linux.com,
        penberg@kernel.org, rientjes@google.com, roman.gushchin@linux.dev,
        42.hyeyoo@gmail.com, linux-mm@kvack.org,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
        chensong_2000@189.cn
Subject: Re: [RFC][PATCH 1/4] mm, page_owner: add folio allocate post
 callback for struct page_owner to make the owner clearer
Message-ID: <ZUz8kTx1eNQkkbFc@casper.infradead.org>
References: <20231109032521.392217-1-jeff.xie@linux.dev>
 <20231109032521.392217-2-jeff.xie@linux.dev>
 <ZUzl0U++a5fRpCQm@casper.infradead.org>
 <CAEr6+EB5q3ksmgYruOVngiwf6KJcrzABchd=Osyk0MiVDGQyQQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAEr6+EB5q3ksmgYruOVngiwf6KJcrzABchd=Osyk0MiVDGQyQQ@mail.gmail.com>
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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?