public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: linux-kernel@vger.kernel.org
Cc: Andreas Dilger <adilger@turbolinux.com>
Subject: Re: hundreds of mount --bind mountpoints?
Date: Mon, 23 Apr 2001 20:16:01 -0400	[thread overview]
Message-ID: <01042320160100.01338@oscar> (raw)

Andreas Dilger wrote:

> Consider, when I was doing some fs benchmark, my inode slab cache was
> over 120k items on a 128MB machine.  At 480 butes per inode, this is
> almost 58 MB, close to half of RAM.  Reducing this to exactly ext2
> sized inodes would save (50 - 27) * 4 * 120k = 11MB of memory (on 32-bit
> systems)!!! (This assumes nfs_inode_info is the largest).

Was this with a recient kernel (post Alexander Viro's dcache pressure fix)?  
If not I suggest rerunning the benchmark.  I had/have a patch to apply pressure 
to the dcache and icache from kswapd but its not been needed here since the above 
fix.

Ed Tomlinson <tomlins@cam.org>

             reply	other threads:[~2001-04-24  0:16 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24  0:16 Ed Tomlinson [this message]
2001-04-24  3:56 ` hundreds of mount --bind mountpoints? Andreas Dilger
2001-04-24 10:01   ` Alexander Viro
2001-04-24 13:27     ` Erik Mouw
2001-04-24 18:47       ` Andreas Dilger
2001-04-24 18:52         ` Alexander Viro
2001-04-24 20:45         ` Erik Mouw
2001-04-25  7:25         ` Christoph Rohland
2001-04-25 18:39     ` Andreas Dilger
2001-04-25 18:47       ` Alexander Viro
  -- strict thread matches above, loose matches on Subject: below --
2001-04-22 16:32 David L. Parsley
2001-04-22 16:41 ` Alexander Viro
2001-04-23 11:43 ` Christoph Rohland
2001-04-23 13:17   ` Ingo Oeser
2001-04-23 14:54     ` Christoph Rohland
2001-04-23 15:23       ` Ingo Oeser
2001-04-23 15:36         ` Alexander Viro
2001-04-23 20:45           ` Ingo Oeser
2001-04-23 20:56             ` Christoph Hellwig
2001-04-23 22:00               ` Ingo Oeser
2001-04-23 22:10                 ` Alexander Viro
2001-04-23 21:19             ` Richard Gooch
2001-04-23 22:42               ` Albert D. Cahalan
2001-04-23 22:49                 ` Richard Gooch
2001-04-23 23:07                   ` Alexander Viro
2001-04-23 23:13                     ` Richard Gooch
2001-04-23 23:24                     ` Rik van Riel
2001-04-23 22:47             ` Andreas Dilger
2001-04-24  1:37             ` Jan Harkes
2001-04-24  2:53               ` Alexander Viro
2001-04-24  9:58                 ` David Woodhouse
2001-04-24 10:07                   ` Alexander Viro
2001-04-24 10:19                     ` David Woodhouse
2001-04-24 10:35                     ` Christoph Rohland
2001-04-24 10:54                       ` Alexander Viro
2001-04-24 12:51                         ` David Woodhouse
2001-04-24 13:34                         ` Christoph Rohland
2001-04-24 16:52                           ` David L. Parsley
2001-04-24 18:36                         ` Andreas Dilger
2001-04-24 18:49                           ` Alexander Viro
2001-04-24 19:11                             ` Andreas Dilger
2001-04-24 22:01                             ` Ingo Oeser
2001-04-24 21:59                 ` Trond Myklebust
2001-04-24 22:09                   ` Alexander Viro
2001-04-24 22:31                     ` Trond Myklebust
2001-04-24  6:33           ` Christoph Rohland
2001-04-23 14:08   ` David L. Parsley
2001-04-23 14:14     ` Alexander 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=01042320160100.01338@oscar \
    --to=tomlins@cam.org \
    --cc=adilger@turbolinux.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox