Received: by 2002:a25:b794:0:0:0:0:0 with SMTP id n20csp2990106ybh; Mon, 5 Aug 2019 10:06:51 -0700 (PDT) X-Google-Smtp-Source: APXvYqwS2PFYOZVnSlTjM8hN0rg0qrzxIIQlbyfI4h3sck0KikINUBCU0/u/Pd3yqmz0o0p0EJ7j X-Received: by 2002:a63:8f55:: with SMTP id r21mr135820565pgn.318.1565024811056; Mon, 05 Aug 2019 10:06:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565024811; cv=none; d=google.com; s=arc-20160816; b=r7iXOfOS/J5rht14MdWAhtmMMmu1CiiaNMmIkf2h7jZcY4UmeNa6DlVdIKZRX58Rm3 QzV4UpAdcs9o0zcvgQXuUa8HLLz2KquzQmPqIPDUOKS5O4eoDxqjLtG27VMdhy4MwAbJ BXIXvU8umdCpImfchu2m6RqbRhzROWmRnOwEwjMVN2eGhPvdc/J32Izl5xsFdO37XfDE nF3my2msufGw6P7PgIpCL6IdJn+4FSlaquNOpDrIZX3kkMflEG6hIELDXvv4cK02pvgB 8D5VgrKzN1SBe+ZOQCATaY29mNCa7BrVROMpdxwvlfrXrL8Ff9U/3j91aiC1EWVbsBUA QsiA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=EpW+/zsfaWUWqnp/CzJ8iSD2ZsdUd34jJeLFlQmjMJk=; b=r6VqWVQNYSc7ouUyBT8EDXU8pPaRnGxU1EL+sQFCIMrhNM0ql05XLasmWZ5HtOukp1 8dnZ39X+TX8HUPWE4BbGh5aBn9eICarF/oln1ygUNCXggVoZXnBjK9+UuAgrtRy0pso1 1hkWc/4mQxXSMJ7A6LF1eQxQseWLimR9OvpovNxXYSySQGyN2tYq+u1TqMix473+Nz39 U7qEFyyLWZruqivn+wHrRe9eWW8lxYFLxqrpiaHrm18TcAUDPjR3XIZq+jc7c7q8TXNj uJV5e/l3RkKXg0vyp/D4VKWjvmVFyZ4mo4/lFH7a3TROd77CH3xi+e7dcb8kcUAB/n01 X9Tw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@joelfernandes.org header.s=google header.b=hgyWzkgS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i188si44524942pfe.96.2019.08.05.10.06.34; Mon, 05 Aug 2019 10:06:51 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@joelfernandes.org header.s=google header.b=hgyWzkgS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730096AbfHERFW (ORCPT + 99 others); Mon, 5 Aug 2019 13:05:22 -0400 Received: from mail-pl1-f194.google.com ([209.85.214.194]:44517 "EHLO mail-pl1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730146AbfHERFV (ORCPT ); Mon, 5 Aug 2019 13:05:21 -0400 Received: by mail-pl1-f194.google.com with SMTP id t14so36687692plr.11 for ; Mon, 05 Aug 2019 10:05:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelfernandes.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=EpW+/zsfaWUWqnp/CzJ8iSD2ZsdUd34jJeLFlQmjMJk=; b=hgyWzkgSkWIkAiyvGZ+G+xjb4IZCoTupPLFm8KMlB2b4hKbMxa1b+uIr1iRdua+wqE QC4A3wju5EZMPMzUeRrpvG6gxy5MEYfQ82W1fGN8SHtXC5yuCxMcBGlIpCV6ZH3OP4zQ UMkuRWp/Da9107v0m9+9yab3KvcgH65HHQUcA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=EpW+/zsfaWUWqnp/CzJ8iSD2ZsdUd34jJeLFlQmjMJk=; b=U12p3KrO2s+yM4iYyZm5gcGj20m+e0uToJJbwsg05lUbr6WM88HGVpHV+DyUQsZKG3 lyoLGvNKVGC8gVPJJ1/3H9ak7/tZWBT+4ptreH7ekYHAVd0grQKc/KEd7xG4LlmZXxX0 +ZzWRIn0PmdpC+jku6nRLsgbpef+5ymGKN5lXCYVUdUU2/Aoe5oCnZ2EMSgevE0xVLEk g0TwLEO3YtIsjswqSntfBLgk+RtkeKgy7hZ3KlQAQA6Y5ynG49FFnLCOGG4KkUFnBypY RDQ3sGn6MgDI3yV3EPJwJ34bwYzE5BwTbG4Se3M5pHN5mmNtuiCKtJwQ62TMNpcj6pR+ eoig== X-Gm-Message-State: APjAAAUtPEZWJb5HNUvrQfj2y8zwvM8vbBHoi0Ag/uo0AjLc8bzJdGuD UGcTK5CSwLWMUXj5prPnfneNT+31 X-Received: by 2002:a17:902:9a95:: with SMTP id w21mr61715428plp.126.1565024719760; Mon, 05 Aug 2019 10:05:19 -0700 (PDT) Received: from joelaf.cam.corp.google.com ([2620:15c:6:12:9c46:e0da:efbf:69cc]) by smtp.gmail.com with ESMTPSA id p23sm89832934pfn.10.2019.08.05.10.05.16 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 05 Aug 2019 10:05:19 -0700 (PDT) From: "Joel Fernandes (Google)" To: linux-kernel@vger.kernel.org Cc: "Joel Fernandes (Google)" , Mike Rapoport , Sandeep Patil , Alexey Dobriyan , Andrew Morton , Borislav Petkov , Brendan Gregg , Catalin Marinas , Christian Hansen , dancol@google.com, fmayer@google.com, "H. Peter Anvin" , Ingo Molnar , joelaf@google.com, Jonathan Corbet , Kees Cook , kernel-team@android.com, linux-api@vger.kernel.org, linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, Michal Hocko , minchan@kernel.org, namhyung@google.com, paulmck@linux.ibm.com, Robin Murphy , Roman Gushchin , Stephen Rothwell , surenb@google.com, Thomas Gleixner , tkjos@google.com, Vladimir Davydov , Vlastimil Babka , Will Deacon Subject: [PATCH v4 5/5] doc: Update documentation for page_idle virtual address indexing Date: Mon, 5 Aug 2019 13:04:51 -0400 Message-Id: <20190805170451.26009-5-joel@joelfernandes.org> X-Mailer: git-send-email 2.22.0.770.g0f2c4a37fd-goog In-Reply-To: <20190805170451.26009-1-joel@joelfernandes.org> References: <20190805170451.26009-1-joel@joelfernandes.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patch updates the documentation with the new page_idle tracking feature which uses virtual address indexing. Reviewed-by: Mike Rapoport Reviewed-by: Sandeep Patil Signed-off-by: Joel Fernandes (Google) --- .../admin-guide/mm/idle_page_tracking.rst | 43 ++++++++++++++++--- 1 file changed, 36 insertions(+), 7 deletions(-) diff --git a/Documentation/admin-guide/mm/idle_page_tracking.rst b/Documentation/admin-guide/mm/idle_page_tracking.rst index df9394fb39c2..9eef32000f5e 100644 --- a/Documentation/admin-guide/mm/idle_page_tracking.rst +++ b/Documentation/admin-guide/mm/idle_page_tracking.rst @@ -19,10 +19,14 @@ It is enabled by CONFIG_IDLE_PAGE_TRACKING=y. User API ======== +There are 2 ways to access the idle page tracking API. One uses physical +address indexing, another uses a simpler virtual address indexing scheme. -The idle page tracking API is located at ``/sys/kernel/mm/page_idle``. -Currently, it consists of the only read-write file, -``/sys/kernel/mm/page_idle/bitmap``. +Physical address indexing +------------------------- +The idle page tracking API for physical address indexing using page frame +numbers (PFN) is located at ``/sys/kernel/mm/page_idle``. Currently, it +consists of the only read-write file, ``/sys/kernel/mm/page_idle/bitmap``. The file implements a bitmap where each bit corresponds to a memory page. The bitmap is represented by an array of 8-byte integers, and the page at PFN #i is @@ -74,6 +78,31 @@ See :ref:`Documentation/admin-guide/mm/pagemap.rst ` for more information about ``/proc/pid/pagemap``, ``/proc/kpageflags``, and ``/proc/kpagecgroup``. +Virtual address indexing +------------------------ +The idle page tracking API for virtual address indexing using virtual frame +numbers (VFN) for a process ```` is located at ``/proc//page_idle``. +It is a bitmap that follows the same semantics as +``/sys/kernel/mm/page_idle/bitmap`` except that it uses virtual instead of +physical frame numbers. + +This idle page tracking API does not deal with PFN so it does not require prior +lookups of ``pagemap``. This is an advantage on some systems where looking up +PFN is considered a security issue. Also in some cases, this interface could +be slightly more reliable to use than physical address indexing, since in +physical address indexing, address space changes can occur between reading the +``pagemap`` and reading the ``bitmap``, while in virtual address indexing, the +process's ``mmap_sem`` is held for the duration of the access. + +To estimate the amount of pages that are not used by a workload one should: + + 1. Mark all the workload's pages as idle by setting corresponding bits in + ``/proc//page_idle``. + + 2. Wait until the workload accesses its working set. + + 3. Read ``/proc//page_idle`` and count the number of bits set. + .. _impl_details: Implementation Details @@ -99,10 +128,10 @@ When a dirty page is written to swap or disk as a result of memory reclaim or exceeding the dirty memory limit, it is not marked referenced. The idle memory tracking feature adds a new page flag, the Idle flag. This flag -is set manually, by writing to ``/sys/kernel/mm/page_idle/bitmap`` (see the -:ref:`User API ` -section), and cleared automatically whenever a page is referenced as defined -above. +is set manually, by writing to ``/sys/kernel/mm/page_idle/bitmap`` for physical +addressing or by writing to ``/proc//page_idle`` for virtual +addressing (see the :ref:`User API ` section), and cleared +automatically whenever a page is referenced as defined above. When a page is marked idle, the Accessed bit must be cleared in all PTEs it is mapped to, otherwise we will not be able to detect accesses to the page coming -- 2.22.0.770.g0f2c4a37fd-goog