All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Soboroff <ian.soboroff@nist.gov>
To: linux-kernel@vger.kernel.org
Subject: Relieving lowmem pressure on a highmem box, 2.4
Date: Wed, 25 Jun 2003 15:43:11 -0400	[thread overview]
Message-ID: <m3k7balz8w.fsf@nist.gov> (raw)


I have a Dell server with 12GB of RAM in it which is having a lot of
trouble with lowmem pressure.  wli's bloatmeter script shows that it's
a lot of buffer-heads and inodes.

$ bloatmost | head -4
         buffer_head:   191316KB   211893KB   90.28
         inode_cache:    64813KB    66097KB   98.5
             size-64:       82KB    10871KB    0.75
             size-32:       95KB     5694KB    1.68

$ cat /proc/slabinfo | sort -k 2,2n | tail
size-512            1052   1176    512  132  147    1 :  124   62
dentry_cache        1068   2580    128   86   86    1 :  252  126
blkdev_requests     1200   1200    128   40   40    1 :  252  126
filp                1230   1230    128   41   41    1 :  252  126
size-32             1532  91118     64   42 1571    1 :  252  126
pte_chain           2466  13050    128  157  435    1 :  252  126
size-128            2946   3450    128  115  115    1 :  252  126
vm_area_struct      3192   4830    128  138  161    1 :  252  126
inode_cache       129503 132195    512 18885 18885    1 :  124   62
buffer_head       2043732 2260200     96 56450 56505    1 :  252  126

What's a good solution for this?  I'm not ready to move to 2.5, since
stability is pretty important for us, but patching 2.4 should be OK.
The current kernel is RedHat's 2.4.20-18.8 (SMP, BIGMEM; HIGHMEM
option set to 64GB).

Thanks in advance,
Ian


             reply	other threads:[~2003-06-25 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 19:43 Ian Soboroff [this message]
2003-06-25 20:09 ` Relieving lowmem pressure on a highmem box, 2.4 Martin J. Bligh

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=m3k7balz8w.fsf@nist.gov \
    --to=ian.soboroff@nist.gov \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.