All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: linux-kernel@vger.kernel.org
Subject: dcache leak in 2.6.16-git8
Date: Mon, 27 Mar 2006 07:50:20 +0200	[thread overview]
Message-ID: <200603270750.28174.ak@suse.de> (raw)


A 2GB x86-64 desktop system here is currently swapping itself to death after
a few days uptime.

Some investigation shows this:

inode_cache         1287   1337    568    7    1 : tunables   54   27    8 : slabdata    191    191      0
dentry_cache      1867436 1867643    208   19    1 : tunables  120   60    8 : slabdata  98297  98297      0

Going to reboot it now.

-Andi

             reply	other threads:[~2006-03-27  5:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27  5:50 Andi Kleen [this message]
2006-03-27 11:48 ` dcache leak in 2.6.16-git8 Bharata B Rao
2006-03-27 16:22   ` Andi Kleen
2006-03-28  3:00     ` Andrew Morton
2006-03-28  7:15       ` Andi Kleen
2006-03-29 22:26       ` dcache leak in 2.6.16-git8 II Andi Kleen
2006-03-29 22:50         ` Andrew Morton
2006-03-29 22:53           ` Andi Kleen
2006-03-30  6:41             ` Balbir Singh
2006-03-30  9:50         ` Al Viro
2006-03-30 10:12           ` Al Viro
2006-03-30 10:36             ` Al Viro

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=200603270750.28174.ak@suse.de \
    --to=ak@suse.de \
    --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.