public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin Kowalski <kowalski@datrix.co.za>
To: tomlins@cam.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: memory usage - dentry_cacheg
Date: Thu, 12 Apr 2001 17:30:59 +0200	[thread overview]
Message-ID: <0104121730590X.11986@webman> (raw)
In-Reply-To: <Pine.GSO.4.21.0104120110210.18135-100000@weyl.math.psu.edu> <20010412114617.051FE723C@oscar.casa.dyndns.org>
In-Reply-To: <20010412114617.051FE723C@oscar.casa.dyndns.org>

Hi

I have applied this(Tom's) patch as well as the small change to 
dcache.c(thanx Andreas, David, Alexander and All), I ran some tests and so 
far so good, both the dcache and inode cache entries in slabinfo are keeping 
nice and low even though I tested by creating thousands of files and then 
deleting then. The dentry and icache both pruged succesfully.

Under the high memory usage test 350 mb of swap was left behind after the 
process terminated leaving 750mb of free memory(physical). Why is this??
I did a swapoff which brough the machine to its' knees for the better part of 
2 minutes  and then a swapon and I was left with 170 megs used memory in 
total... I must say that I find it odd that the swap is not cleared if there 
is avaialbe "real" memory. 

Anyway time will tell, I shall see how it performs over the long weekend. 
HOpefully no *crashes*, Thanks to all concerned for their help... I learned 
*lots*.

Regards
MarCin


-----------------------------
     Marcin Kowalski
     Linux/Perl Developer
     Datrix Solutions
     Cel. 082-400-7603
      ***Open Source Kicks Ass***
-----------------------------

  parent reply	other threads:[~2001-04-12 15:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11 11:36 Fwd: Re: memory usage - dentry_cache Marcin Kowalski
2001-04-12  4:48 ` Fwd: Re: memory usage - dentry_cacheg Andreas Dilger
2001-04-12  5:45   ` Alexander Viro
2001-04-12  6:53     ` [PATCH] " Jeff Garzik
2001-04-12  7:10       ` [CFT][PATCH] Re: Fwd: Re: memory usage - dentry_cache Alexander Viro
2001-04-12  8:44         ` David S. Miller
2001-04-12 12:27           ` Marcin Kowalski
2001-04-12 12:43             ` Yoann Vandoorselaere
2001-04-12 13:54             ` Alexander Viro
2001-04-12 17:27           ` Andreas Dilger
2001-04-12  7:00     ` Fwd: Re: memory usage - dentry_cacheg Andreas Dilger
2001-04-12  7:27       ` [race][RFC] d_flags use Alexander Viro
2001-04-12  8:01         ` David S. Miller
2001-04-12  8:06           ` Alexander Viro
2001-04-12 11:46     ` [PATCH] Re: memory usage - dentry_cacheg Ed Tomlinson
2001-04-12 14:56       ` Rik van Riel
2001-04-12 15:12         ` Alexander Viro
2001-04-13  1:34           ` Ed Tomlinson
2001-04-13  2:03             ` Alexander Viro
2001-04-13  4:45               ` Ed Tomlinson
2001-04-13 13:36                 ` Ed Tomlinson
2001-04-12 15:30       ` Marcin Kowalski [this message]
2001-04-14  3:28         ` Paul
2001-04-12 14:34     ` [PATCH] Re: Fwd: " Jan Harkes
2001-04-12 14:50       ` Alexander Viro
2001-04-12 15:07         ` Rik van Riel
2001-04-12 15:27           ` Alexander Viro
2001-04-12 15:42             ` Alexander Viro
2001-04-12 15:48               ` Rik van Riel

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=0104121730590X.11986@webman \
    --to=kowalski@datrix.co.za \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomlins@cam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox