From: Mel Gorman <mgorman@techsingularity.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Raghavendra K T <raghavendra.kt@amd.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Bharata B Rao <bharata@amd.com>, Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Mel Gorman <mgorman@techsingularity.net>
Subject: [PATCH 1/6] sched/numa: Document vma_numab_state fields
Date: Tue, 10 Oct 2023 09:31:38 +0100 [thread overview]
Message-ID: <20231010083143.19593-2-mgorman@techsingularity.net> (raw)
In-Reply-To: <20231010083143.19593-1-mgorman@techsingularity.net>
Document the intended usage of the fields.
Signed-off-by: Mel Gorman <mgorman@techsingularity.net>
---
include/linux/mm_types.h | 30 +++++++++++++++++++++++++++---
1 file changed, 27 insertions(+), 3 deletions(-)
diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
index 36c5b43999e6..0fe054afc4d6 100644
--- a/include/linux/mm_types.h
+++ b/include/linux/mm_types.h
@@ -551,9 +551,33 @@ struct vma_lock {
};
struct vma_numab_state {
- unsigned long next_scan;
- unsigned long next_pid_reset;
- unsigned long access_pids[2];
+ unsigned long next_scan; /* Initialised as time in
+ * jiffies after which VMA
+ * should be scanned. Delays
+ * first scan of new VMA by at
+ * least
+ * sysctl_numa_balancing_scan_delay
+ */
+ unsigned long next_pid_reset; /* Time in jiffies when
+ * access_pids is reset to
+ * detect phase change
+ * behaviour.
+ */
+ unsigned long access_pids[2]; /* Approximate tracking of PIDS
+ * that trapped a NUMA hinting
+ * fault. May produce false
+ * positives due to hash
+ * collisions.
+ *
+ * [0] Previous PID tracking
+ * [1] Current PID tracking
+ *
+ * Window moves after
+ * next_pid_reset has expired
+ * approximately every
+ * VMA_PID_RESET_PERIOD
+ * jiffies.
+ */
};
/*
--
2.35.3
next prev parent reply other threads:[~2023-10-10 8:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 8:31 [PATCH 0/6] sched/numa: Complete scanning of partial and inactive VMAs Mel Gorman
2023-10-10 8:31 ` Mel Gorman [this message]
2023-10-10 9:43 ` [tip: sched/core] sched/numa: Document vma_numab_state fields tip-bot2 for Mel Gorman
2023-10-10 8:31 ` [PATCH 2/6] sched/numa: Rename vma_numab_state.access_pids Mel Gorman
2023-10-10 9:43 ` [tip: sched/core] sched/numa: Rename vma_numab_state::access_pids[] => ::pids_active[], ::next_pid_reset => ::pids_active_reset tip-bot2 for Mel Gorman
2023-10-10 8:31 ` [PATCH 3/6] sched/numa: Trace decisions related to skipping VMAs Mel Gorman
2023-10-10 9:43 ` [tip: sched/core] " tip-bot2 for Mel Gorman
2023-10-10 8:31 ` [PATCH 4/6] sched/numa: Move up the access pid reset logic Mel Gorman
2023-10-10 9:43 ` [tip: sched/core] " tip-bot2 for Raghavendra K T
2023-10-10 8:31 ` [PATCH 5/6] sched/numa: Complete scanning of partial VMAs regardless of PID activity Mel Gorman
2023-10-10 9:43 ` [tip: sched/core] " tip-bot2 for Mel Gorman
2023-10-10 21:47 ` tip-bot2 for Mel Gorman
2023-10-10 8:31 ` [PATCH 6/6] sched/numa: Complete scanning of inactive VMAs when there is no alternative Mel Gorman
2023-10-10 9:23 ` Ingo Molnar
2023-10-10 9:57 ` Mel Gorman
2023-10-10 21:39 ` Ingo Molnar
2023-10-10 11:40 ` Raghavendra K T
2024-02-24 4:50 ` Raghavendra K T
2023-10-10 9:43 ` [tip: sched/core] " tip-bot2 for Mel Gorman
2023-10-10 11:42 ` [PATCH 6/6] " Raghavendra K T
2023-10-10 21:47 ` [tip: sched/core] " tip-bot2 for Mel Gorman
2023-10-10 11:39 ` [PATCH 0/6] sched/numa: Complete scanning of partial and inactive VMAs Raghavendra K T
2023-10-10 21:45 ` Ingo Molnar
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=20231010083143.19593-2-mgorman@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=bharata@amd.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
/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).