From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: aubreylee@gmail.com, svaidy@linux.vnet.ibm.com,
nickpiggin@yahoo.com.au, rgetz@blackfin.uclinux.org,
Michael.Hennerich@analog.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Limit the size of the pagecache
Date: Thu, 25 Jan 2007 12:12:54 +0900 [thread overview]
Message-ID: <20070125121254.a2e91875.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701241841000.12325@schroedinger.engr.sgi.com>
On Wed, 24 Jan 2007 18:41:27 -0800 (PST)
Christoph Lameter <clameter@sgi.com> wrote:
> > But I can't think of the way to show that.
> > ==
> > [kamezawa@aworks src]$ free
> > total used free shared buffers cached
> > Mem: 741604 724628 16976 0 62700 564600
> > -/+ buffers/cache: 97328 644276
> > Swap: 1052216 2532 1049684
> > ==
>
> Could we call the free memory "unused memory" and not talk about free
> memory at all?
>
Ah, maybe it's better.
I met several memory troubles in user's systems in these days. (on older kernels)
Thousands/hundreds of process works on it.
When I explain the cutomers about memory management, I devides memory into..
(1) unused memory --- memory which is not used, in free-list of zones.
(2) reclaimable memory --- page cache, which is reclaimable
clean pages --- can be reclaimed soon
dirty pages --- need to be written back
*BUT* busy pages are unreclaimable.
(3) swappable memory --- user process's pages. basically reclaimable if
swap is available.
shmem pages are included here.
(4) locked memory --- mlocked memory, which is not reclaimable(but movable)
(5) kernel memory --- used by kernel,
(and we can't see how many pages are reclaimable)
We can know the amount of (1) and (5) and total memory.
Basically, (3) = (Total) - (2) - (1).
busy data-set of (2)(3) is not reclaimable. but the amount of busy data-set
is unknown. Many users takes log of 'ps' or 'sar' to estimate their memory
usage. (and sometimes page-cache of 'log-file' eats their memory.....)
The amount of (4) is unknown. But there was a system with 6GB of 8GB
memory was mlocked (--; and OOM works.
I'm sorry that I can't catch up how the current kernel can show memory usage.
I should investigate that.
FYI:
Because some customers are migrated from mainframes, they want to control
almost all features in OS, IOW, designing memory usages.
-Kame
--
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:[~2007-01-25 3:12 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 0:49 Christoph Lameter
2007-01-24 2:53 ` KAMEZAWA Hiroyuki
2007-01-24 3:01 ` Christoph Lameter
2007-01-24 5:47 ` Aubrey Li
2007-01-24 3:00 ` Nick Piggin
2007-01-24 3:14 ` Christoph Lameter
2007-01-24 3:51 ` Aubrey Li
2007-01-24 4:03 ` Nick Piggin
2007-01-26 10:27 ` Andrew Morton
2007-01-24 3:13 ` KAMEZAWA Hiroyuki
2007-01-24 4:30 ` Christoph Lameter
2007-01-24 5:15 ` KAMEZAWA Hiroyuki
2007-01-25 0:32 ` KAMEZAWA Hiroyuki
2007-01-25 2:41 ` Christoph Lameter
2007-01-25 3:12 ` KAMEZAWA Hiroyuki [this message]
2007-01-25 4:28 ` Rik van Riel
2007-01-25 5:19 ` KAMEZAWA Hiroyuki
2007-01-25 5:40 ` Rik van Riel
2007-01-25 6:00 ` KAMEZAWA Hiroyuki
2007-01-26 10:29 ` Andrew Morton
2007-01-26 18:01 ` KAMEZAWA Hiroyuki
2007-01-24 7:04 ` Vaidyanathan Srinivasan
2007-01-24 7:55 ` Peter Zijlstra
2007-01-24 12:50 ` Nick Piggin
2007-01-24 12:58 ` Peter Zijlstra
2007-01-24 14:58 ` Christoph Lameter
2007-01-24 20:06 ` Erik Andersen
2007-01-25 2:40 ` Christoph Lameter
2007-01-25 8:07 ` Vaidyanathan Srinivasan
2007-01-24 14:22 ` Aubrey Li
2007-01-24 14:56 ` Peter Zijlstra
2007-01-25 2:27 ` Aubrey Li
2007-01-24 12:33 ` Vaidyanathan Srinivasan
2007-01-24 14:56 ` Christoph Lameter
2007-01-25 4:17 ` Vaidyanathan Srinivasan
2007-01-25 4:45 ` Rik van Riel
2007-01-25 5:49 ` Vaidyanathan Srinivasan
2007-01-25 16:07 ` Rik van Riel
2007-01-25 17:57 ` Balbir Singh
2007-01-25 6:35 ` Aubrey Li
2007-01-25 6:47 ` Christoph Lameter
2007-01-25 7:49 ` Vaidyanathan Srinivasan
2007-01-25 4:18 ` Rik van Riel
[not found] <7GEEK-4lH-39@gated-at.bofh.it>
[not found] ` <7GLdb-5Uz-13@gated-at.bofh.it>
[not found] ` <7GRix-7fU-1@gated-at.bofh.it>
[not found] ` <7GRLZ-7Uy-29@gated-at.bofh.it>
2007-01-25 14:51 ` Bodo Eggert
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=20070125121254.a2e91875.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=Michael.Hennerich@analog.com \
--cc=aubreylee@gmail.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rgetz@blackfin.uclinux.org \
--cc=svaidy@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