From: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
To: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Documentation/vm/pagemap.txt: document bit WAITERS
Date: Sat, 17 Feb 2018 11:15:43 +0300 [thread overview]
Message-ID: <151885534363.17898.8456668269733387066.stgit@buzz> (raw)
In-Reply-To: <151834540184.176427.12174649162560874101.stgit@buzz>
Signed-off-by: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
---
Documentation/vm/pagemap.txt | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/vm/pagemap.txt b/Documentation/vm/pagemap.txt
index eafcefa15261..eaa46771fa30 100644
--- a/Documentation/vm/pagemap.txt
+++ b/Documentation/vm/pagemap.txt
@@ -71,6 +71,7 @@ There are four components to pagemap:
23. BALLOON
24. ZERO_PAGE
25. IDLE
+ 26. WAITERS
* /proc/kpagecgroup. This file contains a 64-bit inode number of the
memory cgroup each page is charged to, indexed by PFN. Only available when
@@ -127,6 +128,13 @@ Short descriptions to the page flags:
stale in case the page was accessed via a PTE. To make sure the flag
is up-to-date one has to read /sys/kernel/mm/page_idle/bitmap first.
+26. WAITERS
+ Indicates tasks are waiting when bits LOCKED or WRITEBACK will be cleared.
+ They might be blocked by undergoing IO or by contention on page lock.
+ Bit WAITERS might be false-positive, in this case next clear of LOCKED or
+ WRITEBACK will clear WAITERS too. I.e. without LOCKED and WRITEBACK it's
+ false-positive for sure.
+
[IO related page flags]
1. ERROR IO error occurred
3. UPTODATE page has up-to-date data
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2018-02-17 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-11 10:36 [PATCH] proc/kpageflags: add KPF_WAITERS Konstantin Khlebnikov
2018-02-16 23:57 ` Andrew Morton
2018-02-17 8:14 ` Konstantin Khlebnikov
2018-02-21 0:00 ` Andrew Morton
2018-02-17 8:15 ` Konstantin Khlebnikov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=151885534363.17898.8456668269733387066.stgit@buzz \
--to=khlebnikov@yandex-team.ru \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).