The patch titled
vmstat: update comment regarding stat_threshold
has been removed from the -mm tree. Its filename was
vmstat-update-comment-regarding-stat_threshold.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: vmstat: update comment regarding stat_threshold
From: Christoph Lameter <cl@xxxxxxxxx>
Signed-off-by: Christoph Lameter <cl@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/vmstat.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff -puN mm/vmstat.c~vmstat-update-comment-regarding-stat_threshold mm/vmstat.c
--- a/mm/vmstat.c~vmstat-update-comment-regarding-stat_threshold
+++ a/mm/vmstat.c
@@ -321,9 +321,12 @@ static inline void mod_state(struct zone
/*
* The fetching of the stat_threshold is racy. We may apply
* a counter threshold to the wrong the cpu if we get
- * rescheduled while executing here. However, the following
- * will apply the threshold again and therefore bring the
- * counter under the threshold.
+ * rescheduled while executing here. However, the next
+ * counter update will apply the threshold again and
+ * therefore bring the counter under the threshold again.
+ *
+ * Most of the time the thresholds are the same anyways
+ * for all cpus in a zone.
*/
t = this_cpu_read(pcp->stat_threshold);
_
Patches currently in -mm which might be from cl@xxxxxxxxx are
origin.patch
linux-next.patch
mm-remove-unused-zone_idx-variable-from-set_migratetype_isolate.patch
mm-increase-reclaim_distance-to-30.patch
mm-mem-hotplug-update-pcp-stat_threshold-when-memory-hotplug-occur.patch
mm-mem-hotplug-update-pcp-stat_threshold-when-memory-hotplug-occur-fix.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
