From: Yoss <bartek@milc.com.pl>
To: Roberto Nibali <ratz@drugphish.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory leak in 2.4.33-pre1?
Date: Tue, 14 Feb 2006 09:22:46 +0100 [thread overview]
Message-ID: <20060214082246.GB9993@milc.com.pl> (raw)
In-Reply-To: <43F12597.2000006@drugphish.ch>
On Tue, Feb 14, 2006 at 01:34:31AM +0100, Roberto Nibali wrote:
> >You don't have to worry. Simply check /proc/slabinfo, you'll see plenty
> >of memory used by dentry_cache and inode_cache and that's expected. This
>
> Well, 300M dentry and inode is quite a lot for a system that has been up
> at most for 6 days.
It has 3 days uptime. But I wrote in prevoius mail, I rebooted it last
night to downgrade kernel.
--
Bartłomiej Butyn aka Yoss
Nie ma tego złego co by na gorsze nie wyszło.
next prev parent reply other threads:[~2006-02-14 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 21:46 Yoss
2006-02-14 0:05 ` Willy Tarreau
2006-02-14 0:34 ` Roberto Nibali
2006-02-14 4:50 ` Willy Tarreau
2006-02-14 8:22 ` Yoss [this message]
2006-02-14 8:21 ` Yoss
2006-02-14 21:43 ` Willy TARREAU
2006-02-15 9:01 ` Yoss
2006-02-15 20:11 ` Willy Tarreau
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=20060214082246.GB9993@milc.com.pl \
--to=bartek@milc.com.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=ratz@drugphish.ch \
/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