From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6640DC4332F for ; Thu, 9 Nov 2023 15:37:07 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id DF6038D00EB; Thu, 9 Nov 2023 10:37:06 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id D75C18D0073; Thu, 9 Nov 2023 10:37:06 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id C16348D00EB; Thu, 9 Nov 2023 10:37:06 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id ADBEC8D0073 for ; Thu, 9 Nov 2023 10:37:06 -0500 (EST) Received: from smtpin05.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay04.hostedemail.com (Postfix) with ESMTP id 8B5901A0ECB for ; Thu, 9 Nov 2023 15:37:06 +0000 (UTC) X-FDA: 81438819252.05.C2F4F04 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf08.hostedemail.com (Postfix) with ESMTP id D9AAF160002 for ; Thu, 9 Nov 2023 15:37:03 +0000 (UTC) Authentication-Results: imf08.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=C0nU4zM0; spf=none (imf08.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1699544224; a=rsa-sha256; cv=none; b=4+5ueSQigOPvuEOaqF7Suxwodw6WPXrEssNsYhhXTrgm10Ymskt1FS+mRLFck+DWcd3Aqk 2f8TnTqMxTg2QthYAKo+qr620LBcbAwvplB6zfzSf0zqMk+13nTkd2YwuUTGg4gZFAAo54 6ZcpJNdbd3/EMKbzsOi0emeXtEua6EY= ARC-Authentication-Results: i=1; imf08.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=C0nU4zM0; spf=none (imf08.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1699544224; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=NFkxRWLuyVaV5/yNfiI+b9FYk59N9eHUD1UJ8k1Z614=; b=DxMxlMRgiM3q3TJXwI78Zf5ZF3Q85J/3vOegc01YL/S6OkkXSmkXMo3LPyQnUJEiP6+RYR 0n5z0AqkjA3TI5xD+rYpU/RhIfY76Krys4UpOr0e1X/4rty9Pq1ahjQmuo84PDQj5iiicQ ZpvJIEiZUV/Zhq4BVM8Bj/Etg2slhY0= 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 To: Jeff Xie Cc: Jeff Xie , 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: References: <20231109032521.392217-1-jeff.xie@linux.dev> <20231109032521.392217-2-jeff.xie@linux.dev> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: D9AAF160002 X-Stat-Signature: y57wt7ijc7sg85knkrb1krzjjhmebpys X-Rspam-User: X-HE-Tag: 1699544223-590032 X-HE-Meta: U2FsdGVkX18qoz4NM/ZHt2FJlffw0wND3VqOYWaHHVILLVZnFxdkeWAJg91VdaAKmA5jCqWYLrcKJhb9khnLsvF7pk9FGnM5g6AwLFl1ejB/yanPF2Kmt0dQ2YSGx8ef6V8xYvnQ4ZO/fdk0H/8XeVeJ41VnI8umU3uO+RSQNXqm7C8Fc3Xyq+1GsaS16pEGTMkCtAFSX0kYB8ScewkU916YXKV/pk4+pJHAx9stlwToSf05ceGymwid8qllgrZUTy33pdXK5l6k1OkynvDEnOhKXwCp+uoh9rYdLHA3rqhza3IcGg47q795lUOOrRb809ptaAJppi7qBX5C/KWe2G1EJE/Xi0sDwKYir0ftkuOqpN9nuNZl58u9fG8fcr9Zt0DDyvaWgCITw5FiFi3MCrrYUNqXn6k/WuwA9nWutfbO0YcsfTk/52D5iWoVfKHtGCLPEamKKeYNUakPGtbae4F2X8mRxBob+ym0k/A5sZ2YMA4sc7fMPTdeRA33nNUFYI9IUGn/h/Tu37hFYtruTMNW2HxZyuSWD1L6owUoB5Lg/uuYdVyRKpDSdhIU/o93m+H6SxMm9K28f0YKw+o+Wp9uAKdxrDNsN2HyJVA7OIv5Opwg0pSy1rFDcqgOGf7AX6VvfS2ODmwPPOhH51h29zavucai770YrHIqlwWUXxEVkKTy3Tc+f2v0GbRYMHxphqK/nVCyzV74CnVtgW7JXqT4+XU7J0BDHBJ29ISeoqUBYEmgeHNe543IPVVOXhAvFYz9UXIEaTSM3oo+/Pwwm9yohsdnZuVmtImKsaHSISkI5z4+6PJNQA1Cm7qzGVGA2Ja1SqoYk0fib3TnGVQmH+KaYRWtJVxjYZ2CByhDyYMPLGDeqz1XKarugvrQtWuDpkgj7If9uty4jATJbjDlgf+/Ti5lmgasEe4rXFkhFKr7wVx2qmKCepWt4Zzj/bA20UOGA+61j7hEctTugrs 4wGssyK9 kOcpc4nkpeop4WVMZ3s6YBFs0sfog+Bv389Fd96/SkWAi4D8FPnuX+K49s7BS1XSJVYcG5OZpqvBBBMbE415vnsh6cQxR2899xi/+/XqC+KQMYCJu8ysYwodOnTkVdj9taHswYt1hjdTq9ujckscJAVRa7J15hRSvbn+Ec1JhA53lcXuN/hczmcwqR5lbZlKE/sCGS54COHTiXlK9wUdX1sk+cSIdFNtpF9H6+1XslSgCv9zxI6zLXnjWF6L3bpOsz57z X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: 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?