linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Westerdale, John" <John.Westerdale@stryker.com>
To: linux-mm@kvack.org
Subject: Difference between CommitLimit and Comitted_AS?
Date: Wed, 1 Dec 2010 13:40:18 -0500	[thread overview]
Message-ID: <B13AEDEE265EDB4182EA8B932E33033D13A904B7@SOSEXCHCL02.howost.strykercorp.com> (raw)

Hi All,

Am interested in differentiating the meaning of Commit* and Vmalloc*.

I had thought that the Committed_AS was the sum of memory allocations,
and Commit_Limit was the available memory to serve this from.

That said, I winced when I saw that Committed_AS was almost twice the
Commit__Limit.

Vmalloc looks inconsequential, but, the Commit* numbers must be there
for a reason.

Is it safe to continue running with such a perceived over-commit?

Is this evidence of a leak or garbage collection issues?

This system functions as an App/Web front end using  Tomcat servelet
engine, FWIW.

Thanks

John Westerdale


MemTotal:     16634464 kB
MemFree:      11077520 kB
Buffers:        420768 kB
Cached:        4379000 kB
SwapCached:          0 kB
Active:        4577960 kB
Inactive:       685344 kB
HighTotal:    15859440 kB
HighFree:     10987632 kB
LowTotal:       775024 kB
LowFree:         89888 kB
SwapTotal:     4194296 kB
SwapFree:      4194296 kB
Dirty:              12 kB
Writeback:           0 kB
AnonPages:      462748 kB
Mapped:          65420 kB
Slab:           260144 kB
PageTables:      21712 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:  12511528 kB
Committed_AS: 22423356 kB
VmallocTotal:   116728 kB
VmallocUsed:      6600 kB
VmallocChunk:   109612 kB
HugePages_Total:     0
HugePages_Free:      0
HugePages_Rsvd:      0
Hugepagesize:     2048 kB	

--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2010-12-01 18:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 18:40 Westerdale, John [this message]
2010-12-02  1:41 ` KOSAKI Motohiro
2010-12-02  2:15   ` Westerdale, John
2010-12-02  2:30   ` Westerdale, John
2010-12-02  2:50     ` KOSAKI Motohiro

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=B13AEDEE265EDB4182EA8B932E33033D13A904B7@SOSEXCHCL02.howost.strykercorp.com \
    --to=john.westerdale@stryker.com \
    --cc=linux-mm@kvack.org \
    /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