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 7EF1CC433F5 for ; Thu, 10 Feb 2022 21:38:16 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 024BB6B0075; Thu, 10 Feb 2022 16:38:16 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id F14AE6B0078; Thu, 10 Feb 2022 16:38:15 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id DB65F6B007B; Thu, 10 Feb 2022 16:38:15 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0044.hostedemail.com [216.40.44.44]) by kanga.kvack.org (Postfix) with ESMTP id CEFFE6B0075 for ; Thu, 10 Feb 2022 16:38:15 -0500 (EST) Received: from smtpin11.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id 9743D180C11E6 for ; Thu, 10 Feb 2022 21:38:15 +0000 (UTC) X-FDA: 79128183750.11.0572961 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf03.hostedemail.com (Postfix) with ESMTP id 2EF0020005 for ; Thu, 10 Feb 2022 21:38:14 +0000 (UTC) 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=yiMGkSWaUlInyUsSv6Ymz5MFl5rNEExeyed6yGoVqQo=; b=UIBM663WVp45nBpTuklKQYIaOO qIqrGLpntoMuj+w0Zjrsb/3bZRZJHEEBxo01/e5j3RYuA16k+JKr4fXCfwg+B99MF5J+1bLJ+Jxsb 3k8e1hjG5sxhZ9+FHYVTUSLLfp6CtesC8oHLlIKQvubiwHmjfQp10vYPT10He77uRiHG23oMbvVaT hbtgH4yrj9vzhechikN/jUpAujlWHmSBPuF4DwpgNoDDB+kk0W8w+9iAabVzgoCun/4jStR/hmaq+ FafNBU3pb8iFAL7unJt95dvc82gwXZa10B2otIddSZzFA2j7wS3Y6c4RwzGAGaj0raGgYGzcSGNPG hk7iEN6w==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1nIH81-009n2P-Of; Thu, 10 Feb 2022 21:37:25 +0000 Date: Thu, 10 Feb 2022 21:37:25 +0000 From: Matthew Wilcox To: Yu Zhao Cc: Andrew Morton , Johannes Weiner , Mel Gorman , Michal Hocko , Andi Kleen , Aneesh Kumar , Barry Song <21cnbao@gmail.com>, Catalin Marinas , Dave Hansen , Hillf Danton , Jens Axboe , Jesse Barnes , Jonathan Corbet , Linus Torvalds , Michael Larabel , Mike Rapoport , Rik van Riel , Vlastimil Babka , Will Deacon , Ying Huang , linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, page-reclaim@google.com, x86@kernel.org, Brian Geffon , Jan Alexander Steffens , Oleksandr Natalenko , Steven Barrett , Suleiman Souhlal , Daniel Byrne , Donald Carr , Holger =?iso-8859-1?Q?Hoffst=E4tte?= , Konstantin Kharlamov , Shuang Zhai , Sofia Trinh Subject: Re: [PATCH v7 04/12] mm: multigenerational LRU: groundwork Message-ID: References: <20220208081902.3550911-1-yuzhao@google.com> <20220208081902.3550911-5-yuzhao@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220208081902.3550911-5-yuzhao@google.com> X-Rspamd-Server: rspam11 X-Rspam-User: X-Stat-Signature: 3n7sk6e7u3nbgkyiwjswmn79f391g5cm Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=infradead.org header.s=casper.20170209 header.b=UIBM663W; dmarc=none; spf=none (imf03.hostedemail.com: domain of willy@infradead.org has no SPF policy when checking 90.155.50.34) smtp.mailfrom=willy@infradead.org X-Rspamd-Queue-Id: 2EF0020005 X-HE-Tag: 1644529094-256054 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: On Tue, Feb 08, 2022 at 01:18:54AM -0700, Yu Zhao wrote: > Evictable pages are divided into multiple generations for each lruvec. > The youngest generation number is stored in lrugen->max_seq for both > anon and file types as they're aged on an equal footing. The oldest > generation numbers are stored in lrugen->min_seq[] separately for anon > and file types as clean file pages can be evicted regardless of swap > constraints. These three variables are monotonically increasing. > > Generation numbers are truncated into order_base_2(MAX_NR_GENS+1) bits > in order to fit into the gen counter in folio->flags. Each truncated > generation number is an index to lrugen->lists[]. The sliding window > technique is used to track at least MIN_NR_GENS and at most > MAX_NR_GENS generations. The gen counter stores (seq%MAX_NR_GENS)+1 > while a page is on one of lrugen->lists[]. Otherwise it stores 0. > > There are two conceptually independent processes (as in the > manufacturing process): "the aging", which produces young generations, > and "the eviction", which consumes old generations. They form a > closed-loop system, i.e., "the page reclaim". Both processes can be > invoked from userspace for the purposes of working set estimation and > proactive reclaim. These features are required to optimize job > scheduling (bin packing) in data centers. The variable size of the > sliding window is designed for such use cases [1][2]. > > To avoid confusions, the terms "hot" and "cold" will be applied to the > multigenerational LRU, as a new convention; the terms "active" and > "inactive" will be applied to the active/inactive LRU, as usual. [...] > +++ b/include/linux/page-flags-layout.h > @@ -26,6 +26,14 @@ > > #define ZONES_WIDTH ZONES_SHIFT > > +#ifdef CONFIG_LRU_GEN > +/* LRU_GEN_WIDTH is generated from order_base_2(CONFIG_NR_LRU_GENS + 1). */ > +#define LRU_REFS_WIDTH (CONFIG_TIERS_PER_GEN - 2) > +#else > +#define LRU_GEN_WIDTH 0 > +#define LRU_REFS_WIDTH 0 > +#endif /* CONFIG_LRU_GEN */ I'm concerned about the number of bits being used in page->flags. It seems to me that we already have six bits in use to aid us in choosing which pages to reclaim: referenced, lru, active, workingset, reclaim, unevictable. What I was hoping to see from this patch set was reuse of those bits. That would give us 32 queues in total. Some would be special (eg pages cannot migrate out of the unevictable queue), but it seems to me that you effectively have 4 queues for active and 4 queues for inactive at this point (unless I misunderstood that). I think we need special numbers for: Not on the LRU and Unevictable, but that still leaves us with 30 generations to split between active & inactive. But maybe we still need some of those bits? Perhaps it's not OK to say that queue id 0 is !LRU, queue 1 is unevictable, queue #2 is workingset, queues 3-7 are active, queues 8-15 are various degrees of inactive. I'm assuming that it's not sensible to have a page that's marked as both "reclaim" and "workingset", but perhaps it is. Anyway, I don't understand this area well enough. I was just hoping for some simplification.