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 AE963C3ABAA for ; Thu, 1 May 2025 18:39:25 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 580746B0088; Thu, 1 May 2025 14:39:23 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 5096C6B0089; Thu, 1 May 2025 14:39:23 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3A9606B008A; Thu, 1 May 2025 14:39:23 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 157946B0088 for ; Thu, 1 May 2025 14:39:23 -0400 (EDT) Received: from smtpin12.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 3856D80839 for ; Thu, 1 May 2025 18:39:24 +0000 (UTC) X-FDA: 83395201848.12.355C871 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf19.hostedemail.com (Postfix) with ESMTP id 083E11A0005 for ; Thu, 1 May 2025 18:39:17 +0000 (UTC) Authentication-Results: imf19.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=Dzu19DB+; dmarc=none; spf=none (imf19.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1746124762; a=rsa-sha256; cv=none; b=jHZGUZoyJtluViR24iyYVRSJgNCW1SLKYIbnzmFZVU3+Xxi1Fjt5u63ElxtThUlGGes+sp gfTcgTCleGk6FlnkC2FWrZGvTeHr4oNpf99eFeYSuGJgscJoft63AtYNFrrCW+Z7Pun3kb bEUqjcyyFw+R348/GQL9qRktLDzegOc= ARC-Authentication-Results: i=1; imf19.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=Dzu19DB+; dmarc=none; spf=none (imf19.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1746124762; 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=ZRGNnZIibSpQ4Mgi891kL5PuMPNjxsoIayZPZFiUSA8=; b=1aaSmIoI6Z7OIaluMBPff9WP8euS0+krS0trvAh9V+F5uF58u4nr9JVSocF/Kaig+e4ucb 0a5jl0d0c8FD3/WjAvRbKUsbHW600yMFuCGolopgChiqnrGpSBS6nBBK+OOlAWtdNBKvCv S8dhFqrVbo7gGrsvGQCVjdKuoIHb5p0= 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=ZRGNnZIibSpQ4Mgi891kL5PuMPNjxsoIayZPZFiUSA8=; b=Dzu19DB+UuRCz7HSqaOtKYImi+ 6UyQ7BtWPDSVCV8lRzh6nOrPbePI3MqXWkp7bsr186yx15qq8g11qR7f0JORQ6dxlSRLz4HHHzf66 AD4spY2/bSYSrm6kpGq2lY+YakjNlmFIS/UufZ2IkPvych1wzKDkyhL1XTQIe4yUNgLkMDJHw6m2N dWRRf/7tdpSifsKT8ugr6/csSeT3MVkYwrKrtUKsGqVQ+fA++/YzG+LZWhjTajISfHME8suR1jS8+ 6Jna9s7jnqgd1RYIxR9cB4EcAXDEAEidGbBn3zkboyWsK6s5P6J1zd7Nw75M4FgMznKDBzi+GGYRI r/iicqWg==; Received: from willy by casper.infradead.org with local (Exim 4.98.2 #2 (Red Hat Linux)) id 1uAYnV-00000005ULO-3bFC; Thu, 01 May 2025 18:38:13 +0000 Date: Thu, 1 May 2025 19:38:13 +0100 From: Matthew Wilcox To: Juan Yescas Cc: Catalin Marinas , Will Deacon , Andrew Morton , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, tjmercier@google.com, isaacmanjarres@google.com, surenb@google.com, kaleshsingh@google.com, Vlastimil Babka , "Liam R. Howlett" , Lorenzo Stoakes , David Hildenbrand , Mike Rapoport , Zi Yan , Minchan Kim Subject: Re: [PATCH] mm: Add ARCH_FORCE_PAGE_BLOCK_ORDER to select page block order Message-ID: References: <20250501052532.1903125-1-jyescas@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250501052532.1903125-1-jyescas@google.com> X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: 083E11A0005 X-Stat-Signature: ic455kre9m376ytyjwm65tz31a7b58xe X-Rspam-User: X-HE-Tag: 1746124757-778906 X-HE-Meta: U2FsdGVkX187FKr1UM4nYmysEky56H14yzCEqAA7aGy7w+6IEQrafgVx6P9iOpsIAkZYYlXObK14kXEAWvlGBokmXEx2Pp7ViqZiAT2Bxx9u422Tk+qCekQgJs7ey/2ZswKwou5KJQk7YbXKCWiXhn0LLWBVOz4AwQLpeA7WXHNKaWHGcyraxjPv4NhdeeGI1FM9RGRR9W8mTpy6LWJmhPMOEK0l23YsrzeOzspMDD4KfHkpi+WoOYUTcJ9+7RIs30FVtlakzLoe13Rm8IM4eul76VGtwd/hOnS2rFKPArGzz/Mxypac7JhknYv+WeuV/x+OsVlzKZ7cnW3GQk5uFRszYqy/C60a9vhZFsaenPzGsVm7Lqf0T+ettK7qt/k8E3PzmNh7wHKrFZrmYm91a2PQ0HK7BSqHJr6KOba+QEc2050S7lWK/oxoCQzGvhOUlKKaoemA/BqKXhMyL9Iy/eJu+eyAYNY8D9vW5tTJaMZ6Kcqy0ZRvr2R81lJg9WVR4PS8/uD1OVdF1itNJeQPpJ8fcJhGas1XjTLZl+7uATzW8bqC5uLwYifj771PgM5juNTtTORhLrAF2dUNM9UikO3OnjdR+bmd6S3duXoRpVgXKojCs2NI/tPeNSFqErkhF6emJps0ov36edH47aaJzuCits6K8+FGx38KOnO2S1noNRlvEK+6YdMCdXEiw2WgfiEhPuXjaDqbX71gCEjYtJ3CL5utIAQlAQqizgUTtxSnuPdWGDwCf12fjWgquEO1zu3fXnWekKE39k4inPUkeHD6UrTrHkECxDiFER4IilDab4gjYy5c0IgqBH4aSw4NtQWD1KmbH4WonEeX91yGFkdjwF2hnP8rV+ahyBKra61CMkXPt+WieoAGGC58sGZ1JUBsuSbf6rErtvqWQyYGSGiFwDYjthhkOjWy8ubFO1YZ/Osee+Ck0w4ujMfQF3bKKw0CynMf8aUJt9l5wMN /CkAY2dL 7HWngopb2WJM1h/PkghPAf43/ZqfVbQ6xSP316NYOkN/r/oTRiCIbmZbWMOkGEs0zLC76WD2S7KZLDwo9UhuQyqpHYDWNfft8YwfeqRjV6uTmSZU+IJxltPchuqFZWpjpuIJfKxx3ssrPuWy5ClTXZ29wKR8SzewWz7m14tbO1W3ms5d73OfCq3s6hH2GxXrnbPG9D+bks4zwXevOR5xbQd0ppolwH3lPvkenGK2BGjovMyu4zCfEgRTRcoxT/5JNHQmADS7SXr/uYrEhk5gjGlQoOw== 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 Wed, Apr 30, 2025 at 10:25:11PM -0700, Juan Yescas wrote: > Problem: On large page size configurations (16KiB, 64KiB), the CMA > alignment requirement (CMA_MIN_ALIGNMENT_BYTES) increases considerably, > and this causes the CMA reservations to be larger than necessary. > This means that system will have less available MIGRATE_UNMOVABLE and > MIGRATE_RECLAIMABLE page blocks since MIGRATE_CMA can't fallback to them. > > The CMA_MIN_ALIGNMENT_BYTES increases because it depends on > MAX_PAGE_ORDER which depends on ARCH_FORCE_MAX_ORDER. The value of > ARCH_FORCE_MAX_ORDER increases on 16k and 64k kernels. Sure, but why would any architecture *NOT* want to set this? This seems like you're making each architecture bump into the problem by itself, when the real problem is that the CMA people never thought about this and should have come up with better defaults.