public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zou Min <zoum@comp.nus.edu.sg>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Josh Grebe <squash@primary.net>, Jan Harkes <jaharkes@cs.cmu.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: Question about memory usage in 2.4 vs 2.2
Date: Wed, 21 Mar 2001 17:28:00 +0800	[thread overview]
Message-ID: <20010321172800.A11353@comp.nus.edu.sg> (raw)
In-Reply-To: <Pine.LNX.4.21.0103201403440.2405-100000@scarface.primary.net> <Pine.LNX.4.21.0103201857170.3750-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.21.0103201857170.3750-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on Tue, Mar 20, 2001 at 07:18:43PM -0300

> > slabinfo reports:
> > 
> > inode_cache       189974 243512    480 30439 30439    1 :  124   62
> > dentry_cache      201179 341940    128 11398 11398    1 :  252  126
>                                       ^
>   <name>            <used> <allocd>   |  <used> <allocd>
>                      <in objects>  <size>   <in pages>
> 

Then how to interpret slabinfo in 2.2.16 box? 
e.g. grep cache /proc/slabinfo

kmem_cache            32     42
skbuff_head_cache   2676   2730
dentry_cache       15626  16988
files_cache          103    108
uid_cache             10    127
slab_cache            85    126
what does those numbers mean?

Furthermore, are those cache info above reported as part of the total
cache in /proc/meminfo ? 

Lastly, which cache can be reclaimed, and which can't?

I am doing some memory measurements in 2.2.16 linux box. Thanks in advance!

-- 
Cheers!
--Zou Min 


  parent reply	other threads:[~2001-03-21  9:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-19  2:07 /proc/cpuinfo for Intel P4 D850GB asenec
2001-03-19  2:33 ` davej
2001-03-19  3:14 ` 2.4.3-pre4: Unable to handle kernel NULL pointer dereference at virtual address 000000fb Shawn Starr
2001-03-19 12:02 ` /proc/cpuinfo for Intel P4 D850GB David Weinehall
2001-03-19 21:58 ` 2.4.3-pre4: Unable to handle kernel NULL pointer dereference at virtual address 000000fb Shawn Starr
2001-03-20 17:01 ` Question about memory usage in 2.4 vs 2.2 Josh Grebe
2001-03-20 17:32   ` Jakob Østergaard
2001-03-20 20:29     ` Josh Grebe
2001-03-21 19:16       ` Jan Harkes
2001-03-21 19:54         ` Rik van Riel
2001-03-20 18:54   ` Jan Harkes
2001-03-20 20:29     ` Josh Grebe
2001-03-20 22:18       ` Rik van Riel
2001-03-20 22:29         ` Juha Saarinen
2001-03-21  9:28         ` Zou Min [this message]
2001-03-21  9:51           ` Andreas Dilger
2001-03-21 10:56             ` Zou Min
  -- strict thread matches above, loose matches on Subject: below --
2001-03-21 10:14 Manfred Spraul
2001-03-21 17:42 ` Josh Grebe

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=20010321172800.A11353@comp.nus.edu.sg \
    --to=zoum@comp.nus.edu.sg \
    --cc=jaharkes@cs.cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=squash@primary.net \
    /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