Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp1533275pxt; Sat, 7 Aug 2021 14:30:44 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyu24+IkdeLbfFmwsEFFsPcga2srOX6oJ5Q5m5osDyocIaZ+vkzXvoNLDsso+oj4zxnDyH/ X-Received: by 2002:a92:cac5:: with SMTP id m5mr314532ilq.66.1628371844530; Sat, 07 Aug 2021 14:30:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628371844; cv=none; d=google.com; s=arc-20160816; b=CF1XlabK9AnZ5tCXVp0TpyriZYDgXAoPfrK6MrBsmPGXM9FlCwQMDMoUdsU6yIAr6e 41NY26PAlglzAZq7QwdWvQdTB8S8tbIspKIS0CDaYKAO37xFFLzQWhmeJ+O1zr2yjQZP xSLY1bD60SlGZ2kE794XVlQ17AvMwoEuKwq6y5d2hdlBr3XvGIGlvws1aywIbwm71Gc6 2ytNHiRHw2IlH+uvjhF3FzYd50Da60f4BMd3WMHLGHu7pya4udRWIKqcBJx6dphmdw5x Y7aGrud6T4rzui1Mjg5TaCtEvndPqvmkpcbQZhJ++oGm4Tt3Ul6KaingnRuWRd5aJ6X7 e+dA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=aA5HS3VKpHetp3gEzc9iEc7bj1aIHq24Bb+xq3Es5LU=; b=hlms34Pji+8dJRcf2V3kAUfB6IObJTQ2RdCbEaXvzXWmQLBjl94fsF/zE9w5i35TFt xh364Rtld5x7KqkpMTy8mx2OegUGAUc98p2ExlpRmEAkLx84kzyzO7EGSDlo/2o+wpkR zkEm4w+RaIacX3te3dDDZRzPRUeSu0iBzbXTO389Hlc0wVwkvt4XvD2/1Ny8zJlp4kc2 jZfDaeva0mAuX1jeeViIS/Ye7Ww1OYar2P1VmDUq7Mliry2CxDT8jBBbgUP7nF3VLvI+ XEi1vDiQJsT03VxUvNYYUdQJWv/3bC0IJf8uWHwd61uKZsBx3qBo6Jqj9Xva8KEY4K5x 7cpg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b=ZANN2lpG; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z16si12963968ilo.50.2021.08.07.14.30.08; Sat, 07 Aug 2021 14:30:44 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b=ZANN2lpG; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229777AbhHGVYc (ORCPT + 99 others); Sat, 7 Aug 2021 17:24:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41150 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229517AbhHGVYb (ORCPT ); Sat, 7 Aug 2021 17:24:31 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 49B5AC0613CF for ; Sat, 7 Aug 2021 14:24:13 -0700 (PDT) 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=aA5HS3VKpHetp3gEzc9iEc7bj1aIHq24Bb+xq3Es5LU=; b=ZANN2lpGFk3nRvYarK5XIJERCS +NWy2JNCxNY8Xi5VPTrnA35PD3MBwN1VX1/TbeotRkLWlnE9uGyLrEOAms1Uj+oQrn7pFH2b//W9q pCO1iHwG8qo4Kh5SstGa3R6JtvKOXW3mZhNjtWW0tRJ3VHP4nvelHc3CxVpboE5tVqK+94MPyo6iz ARzIkO/WcEkruk+OoNSXvfG5pdzyj7PFkOg3nOXp4xU+m3lQavDI7OaUtAsAtj0Ml8WlJX00dNnm6 OKXvflohBcntsuD/TJCGb0oivj3nXcoHSORrezQhpl4j1tJOTk6eWTKmlTibiU4nXfYOdVQWwjxZk mu9nrYOA==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1mCTmj-009Smd-Tl; Sat, 07 Aug 2021 21:23:17 +0000 Date: Sat, 7 Aug 2021 22:23:13 +0100 From: Matthew Wilcox To: Hugh Dickins Cc: Zi Yan , Vlastimil Babka , David Hildenbrand , linux-mm@kvack.org, "Kirill A . Shutemov" , Mike Kravetz , Michal Hocko , John Hubbard , linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH 00/15] Make MAX_ORDER adjustable as a kernel boot time parameter. Message-ID: References: <20210805190253.2795604-1-zi.yan@sent.com> <0d374eed-cc52-a656-b338-1156782bdf7e@suse.cz> <6ae6cd92-3ff4-7ed3-b337-a4dfe33da1c@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Aug 07, 2021 at 02:10:55AM +0100, Matthew Wilcox wrote: > This hasn't been helped by the scarce number of 1GB TLB entries in Intel > CPUs until very recently (and even those are hard to come by today). Minor correction to this. I just fixed x86info to work on my Core i7-1165G7 (Tiger Lake, launched about a year ago) and discovered it has: L1 Store Only TLB: 1GB/4MB/2MB/4KB pages, fully associative, 16 entries L1 Load Only TLB: 1GB pages, fully associative, 8 entries L2 Unified TLB: 1GB/4KB pages, 8-way associative, 1024 entries My prior laptop (i7-7500U, Kaby Lake, 2016) has only 4x 1GB TLB entries at the L1 level, and no support for L2 1GB pages. So this speaks to Intel finally taking performance of 1GB TLB entries seriously. Perhaps more seriously than they need to for a laptop with 16GB of memory! There are Xeon-W versions of this CPU, so I imagine that there are versions which can support 1TB or more memory. I still think that 1GB pages are too big for anything but specialist use cases, but those do exist.