From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Eric B Munson <ebmunson@us.ibm.com>,
Mel Gorman <mel@linux.vnet.ibm.com>,
Christoph Lameter <cl@linux-foundation.org>
Subject: Re: meminfo Committed_AS underflows
Date: Wed, 15 Apr 2009 11:04:59 +0900 (JST) [thread overview]
Message-ID: <20090415105033.AC29.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <1239737619.32604.118.camel@nimitz>
> I have a set of ppc64 machines that seem to spontaneously get underflows
> in /proc/meminfo's Committed_AS field:
>
> # while true; do cat /proc/meminfo | grep _AS; sleep 1; done | uniq -c
> 1 Committed_AS: 18446744073709323392 kB
> 11 Committed_AS: 18446744073709455488 kB
> 6 Committed_AS: 35136 kB
> 5 Committed_AS: 18446744073709454400 kB
> 7 Committed_AS: 35904 kB
> 3 Committed_AS: 18446744073709453248 kB
> 2 Committed_AS: 34752 kB
> 9 Committed_AS: 18446744073709453248 kB
> 8 Committed_AS: 34752 kB
> 3 Committed_AS: 18446744073709320960 kB
> 7 Committed_AS: 18446744073709454080 kB
> 3 Committed_AS: 18446744073709320960 kB
> 5 Committed_AS: 18446744073709454080 kB
> 6 Committed_AS: 18446744073709320960 kB
>
> As you can see, it bounces in and out of it. I think the problem is
> here:
>
> #define ACCT_THRESHOLD max(16, NR_CPUS * 2)
> ...
> void vm_acct_memory(long pages)
> {
> long *local;
>
> preempt_disable();
> local = &__get_cpu_var(committed_space);
> *local += pages;
> if (*local > ACCT_THRESHOLD || *local < -ACCT_THRESHOLD) {
> atomic_long_add(*local, &vm_committed_space);
> *local = 0;
> }
> preempt_enable();
> }
>
> Plus, some joker set CONFIG_NR_CPUS=1024.
>
> nr_cpus (1024) * 2 * page_size (64k) = 128MB. That means each cpu can
> skew the counter by 128MB. With 1024 CPUs that means that we can have
> ~128GB of outstanding percpu accounting that meminfo doesn't see. Let's
> say we do vm_acct_memory(128MB-1) on 1023 of the CPUs, then on the other
> CPU, we do vm_acct_memory(-128GB).
>
> The 1023 cpus won't ever hit the ACCT_THRESHOLD. The 1 CPU that did
> will decrement the global 'vm_committed_space' by ~128 GB. Underflow.
> Yay. This happens on a much smaller scale now.
>
> Should we be protecting meminfo so that it spits slightly more sane
> numbers out to the user?
Can you try to this patch? (Oh well, I can't reproduce this underflow
on my small machine)
===============
Dave Hansen reported committed_AS field can underfolow.
> # while true; do cat /proc/meminfo | grep _AS; sleep 1; done | uniq -c
> 1 Committed_AS: 18446744073709323392 kB
> 11 Committed_AS: 18446744073709455488 kB
> 6 Committed_AS: 35136 kB
> 5 Committed_AS: 18446744073709454400 kB
> 7 Committed_AS: 35904 kB
> 3 Committed_AS: 18446744073709453248 kB
> 2 Committed_AS: 34752 kB
> 9 Committed_AS: 18446744073709453248 kB
> 8 Committed_AS: 34752 kB
> 3 Committed_AS: 18446744073709320960 kB
> 7 Committed_AS: 18446744073709454080 kB
> 3 Committed_AS: 18446744073709320960 kB
> 5 Committed_AS: 18446744073709454080 kB
> 6 Committed_AS: 18446744073709320960 kB
Because NR_CPU can be greater than 1000. and meminfo_proc_show()
doesn't have underflow check.
this patch have two change.
1. Change NR_CPU to nr_online_cpus()
vm_acct_memory() isn't fast-path. then cpumask_weight() calculation
isn't so expensive and the parameter for scalability issue should
consider number of _physical_ cpus. not theoretical maximum number.
2. Add under-flow check to meminfo_proc_show().
Almost field in /proc/meminfo have underflow check. but Committed_AS
is significant exeption.
it should do.
Reported-by: Dave Hansen <dave@linux.vnet.ibm.com>
Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
---
fs/proc/meminfo.c | 2 ++
mm/swap.c | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
Index: b/fs/proc/meminfo.c
===================================================================
--- a/fs/proc/meminfo.c
+++ b/fs/proc/meminfo.c
@@ -36,6 +36,8 @@ static int meminfo_proc_show(struct seq_
si_meminfo(&i);
si_swapinfo(&i);
committed = atomic_long_read(&vm_committed_space);
+ if (committed < 0)
+ committed = 0;
allowed = ((totalram_pages - hugetlb_total_pages())
* sysctl_overcommit_ratio / 100) + total_swap_pages;
Index: b/mm/swap.c
===================================================================
--- a/mm/swap.c
+++ b/mm/swap.c
@@ -519,7 +519,7 @@ EXPORT_SYMBOL(pagevec_lookup_tag);
* We tolerate a little inaccuracy to avoid ping-ponging the counter between
* CPUs
*/
-#define ACCT_THRESHOLD max(16, NR_CPUS * 2)
+#define ACCT_THRESHOLD max_t(long, 16, num_online_cpus() * 2)
static DEFINE_PER_CPU(long, committed_space);
--
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>
next prev parent reply other threads:[~2009-04-15 2:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 19:33 Dave Hansen
2009-04-15 2:04 ` KOSAKI Motohiro [this message]
2009-04-15 3:34 ` Balbir Singh
2009-04-15 4:10 ` KOSAKI Motohiro
2009-04-15 8:47 ` Balbir Singh
2009-04-27 20:27 ` Andrew Morton
2009-04-28 3:07 ` KOSAKI Motohiro
2009-04-28 3:27 ` Andrew Morton
2009-04-28 4:25 ` KOSAKI Motohiro
2009-04-28 8:17 ` Dave Hansen
2009-04-15 4:12 ` KOSAKI Motohiro
2009-04-15 8:33 ` Alan Cox
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=20090415105033.AC29.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=cl@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=ebmunson@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@linux.vnet.ibm.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