From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: 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 09:33:17 +0100 [thread overview]
Message-ID: <20090415093317.4f937809@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1239737619.32604.118.camel@nimitz>
> 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?
Yes. It used to be accurate but the changes were put in as the memory
accounting value was actually starting to show up in profiles as it
bounced around the CPUs - perhaps the constraint should instead be a
worst case error as percentage of total system memory ?
Alan
--
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:[~2009-04-15 8:31 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
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 [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=20090415093317.4f937809@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--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