Received: by 2002:a05:6a10:8a4d:0:0:0:0 with SMTP id dn13csp179899pxb; Thu, 12 Aug 2021 13:45:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJySJ3AmJg9nj/gBEwgCYqAhlA2XlX/Vky9ORO+ValeCsahxdKUT051Y/XkAFXgjdIi//97q X-Received: by 2002:a17:906:260a:: with SMTP id h10mr5404180ejc.498.1628801141528; Thu, 12 Aug 2021 13:45:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628801141; cv=none; d=google.com; s=arc-20160816; b=u+hlHSMbUyxOoe+6EoeWDxCUtldMWULLlaGD34W7IsxjXbcAU/9gDZ75RmV9caMhxn anrC+qsGWgNR8wwJpxZQTilmwBkERFJP1WYzkCAwpr1BKlUrufq6jdxLMCmP2RvXVwjb iz4JLfA0pNjnQ0W8zkQFpgEreicZv1mk3ZwrfIM7qqjj/uSV3yUHtHdvBTyvYUunRxId T9LsoAsqXkQZVrhapZFluimArjZz2j9SrRj+gQwswTb8ORSGTR65lZWtJR4K6BVu7dTn pcFk/0gHcfEgv6HiamnfuXJkCbJCEfwTZWm7k3UcHWiCn60XfVCT+VUrIKCz8dTTXb8A WMgA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=AEjvfy7gx01zWebDT8EtiaV1tq4TiQpgPAo6mSTkt+o=; b=v6/PfWujn7rTkA0h/uVcy8/Df1MFY1AQuFYCBlEHZDPOuTK8wqCdo1og97RL0gyYZI hQ9H9mBoizRmnoUOeaLf/408YzJ7iAwitD1TfuoBv0kecL6nE4+BYY0Gqqvjdw2jFNRA x1+M44IApJbXShm8n6Xv4+bKsLCHbX8j4X4FcSYUBjfntptfUxv0UV5FNboPFJpNPZW1 dQgyNPjLsvRJZP+f3N/rGfdBxXzuhO0V+ekRL2CqddlCPh4KylSkTjbLevwUr7F+fH8H /qI26+dmVtkmxdONWlrXLJ69bGl1q0a+tr+pj73rJfX4PqsgIr9nM2PV73qNC/edg6wa 8vpQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@linux-foundation.org header.s=korg header.b=MHlUhKi3; 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 ks26si3407234ejb.542.2021.08.12.13.45.13; Thu, 12 Aug 2021 13:45:41 -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=fail header.i=@linux-foundation.org header.s=korg header.b=MHlUhKi3; 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 S236903AbhHLUTv (ORCPT + 99 others); Thu, 12 Aug 2021 16:19:51 -0400 Received: from mail.kernel.org ([198.145.29.99]:57302 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234307AbhHLUTu (ORCPT ); Thu, 12 Aug 2021 16:19:50 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id AC44B6101E; Thu, 12 Aug 2021 20:19:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1628799564; bh=Met7BhuqN1q9Po3dqJQJ6Y0ovIYXHRZjV39nyIWR2KY=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=MHlUhKi3mZoE9MhFJwD6k376NqkGX3yv1mGuBfyiWDaFkimvMJ4XLGvJurLQFvCSw xJ42KQGRuWpefErVY7wS7Xy93VJ+Z6ihqAsNfczrle46YuuX4b70aWb0Yvb3eZl0GZ +u1c8rNyWDP6ZDc5aU0heOiQ5vLJABtPDUcp8bxg= Date: Thu, 12 Aug 2021 13:19:21 -0700 From: Andrew Morton To: SeongJae Park Cc: =?UTF-8?Q? "Valdis_Kl=C4=93tnieks" ?= , SeongJae Park , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: Message-Id: <20210812131921.a1c5c85213290e1729cc72a3@linux-foundation.org> In-Reply-To: <20210812094240.4492-1-sjpark@amazon.de> References: <144813.1628760117@turing-police> <20210812094240.4492-1-sjpark@amazon.de> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 12 Aug 2021 09:42:40 +0000 SeongJae Park wrote: > > +config PAGE_IDLE_FLAG > > + bool "Add PG_idle and PG_young flags" > > + help > > + This feature adds PG_idle and PG_young flags in 'struct page'. PTE > > + Accessed bit writers can set the state of the bit in the flags to let > > + other PTE Accessed bit readers don't disturbed. > > > > This needs to be converted to proper, or at least comprehensible, English.... > > Thank you for the comment. > > How about below? > > --- a/mm/Kconfig > +++ b/mm/Kconfig > @@ -743,9 +743,9 @@ config PAGE_IDLE_FLAG > bool "Add PG_idle and PG_young flags" > select PAGE_EXTENSION if !64BIT > help > - This feature adds PG_idle and PG_young flags in 'struct page'. PTE > - Accessed bit writers can set the state of the bit in the flags to let > - other PTE Accessed bit readers don't disturbed. > + This feature adds 'PG_idle' and 'PG_young' flags in 'struct page'. > + PTE Accessed bit writers can save the state of the bit in the flags > + to let other PTE Accessed bit readers don't get disturbed. How about this? --- a/mm/Kconfig~mm-idle_page_tracking-make-pg_idle-reusable-fix-fix +++ a/mm/Kconfig @@ -743,9 +743,9 @@ config PAGE_IDLE_FLAG bool "Add PG_idle and PG_young flags" select PAGE_EXTENSION if !64BIT help - This feature adds PG_idle and PG_young flags in 'struct page'. PTE - Accessed bit writers can set the state of the bit in the flags to let - other PTE Accessed bit readers don't disturbed. + This adds PG_idle and PG_young flags to 'struct page'. PTE Accessed + bit writers can set the state of the bit in the flags so that PTE + Accessed bit readers may avoid disturbance. config IDLE_PAGE_TRACKING bool "Enable idle page tracking" Also, is there any way in which we can avoid presenting this option to the user? Because most users will have real trouble understanding what this thing is for. Can we simply select it when needed, as dictated by other, higher-level config options?