mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Patrick R. McManus" <mcmanus@ducksong.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory Measurements and Lots of Files and Inodes
Date: Wed, 11 Dec 2002 16:27:32 -0800	[thread overview]
Message-ID: <3DF7D7F4.4347430E@digeo.com> (raw)
In-Reply-To: <20021212002110.GA27532@ducksong.com>

"Patrick R. McManus" wrote:
> 
> ...
> > If you could share your test apps that would help a lot.
> 
> sure! this is the "lots of files" program.

Yep, negative dentries:

      dentry_cache:   149092KB   149092KB  100.0 
  ext3_inode_cache:     3425KB    10102KB   33.90
   radix_tree_node:      594KB     1612KB   36.88
       buffer_head:      543KB     1264KB   42.99


You can monitor these via /proc/slabinfo, or using Bill's bloatmeter
script from http://www.zip.com.au/~akpm/linux/patches/stuff/

> ...
> 
> > On your machine it'll be "all of swap plus all of physical memory
> > minus whatever malloc'ed memory you're using now minus 8-12 megabytes".
> > There isn't much memory which cannot be reclaimed unless you have a
> > huge machine or you're doing odd things.
> 
> this is useful advice, thanks. Basically what the new procps does?

I don't know what procps does.

But your fill-up-all-memory program will certainly do the trick.
Run it, create a huge swapstorm (or get oom-killed if there's no
swap) and then see what `free' says.  That's as much memory as the
kernel will ever give you.

  reply	other threads:[~2002-12-12  0:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 23:52 Patrick R. McManus
2002-12-12  0:09 ` Andrew Morton
2002-12-12  0:21   ` Patrick R. McManus
2002-12-12  0:27     ` Andrew Morton [this message]
2002-12-13  8:39 ` David Schwartz

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=3DF7D7F4.4347430E@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcmanus@ducksong.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

Powered by JetHome