diff options
| author | Christoph Lameter <cl@linux.com> | 2011-04-14 15:21:58 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2011-04-14 16:06:54 -0700 |
| commit | d3bc2367180f7ee6afe4ee6e886bfba3ad4eb290 (patch) | |
| tree | 5adabc909d7ba380d845b9918de83e437e741854 | |
| parent | 9f6ae448bfc6cdf40279f43bb0b4fd159edc4e0a (diff) | |
vmstat: update comment regarding stat_threshold
Signed-off-by: Christoph Lameter <cl@linux.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
| -rw-r--r-- | mm/vmstat.c | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/mm/vmstat.c b/mm/vmstat.c index 772b39b87d9..8cb0f0a703e 100644 --- a/mm/vmstat.c +++ b/mm/vmstat.c @@ -321,9 +321,12 @@ static inline void mod_state(struct zone *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); |