From: "Ray Lee" <madrabbit@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: userspace pagecache management tool
Date: Sat, 3 Mar 2007 14:58:48 -0800 [thread overview]
Message-ID: <2c0942db0703031458i540c496fib892240619faa9b2@mail.gmail.com> (raw)
In-Reply-To: <20070303122935.f1ab0067.akpm@linux-foundation.org>
On 3/3/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> It is to address the "waah, backups fill my memory with pagecache" and the
> "waah, updatedb swapped everything out" and the "waah, copying a DVD
> gobbled all my memory" problems.
Is the updatedb problem really due to pagecache?
> When running
>
> pagecache-management.sh dd if=100-mb-file of=foo
> or
> pagecache-management.sh cp -a /usr/src/linux-2.6.20 /usr/src/foo
>
> the amount of pagecache in the machine is pretty much unaltered. Maybe a
> megabyte of additional cache in the second case, because of ext3 indirect
> blocks.
ray@phoenix:~/work/home/pagecache-management$ grep ext3_i
/proc/slabinfo; ./pagecache-management.sh sudo updatedb; grep ext3_i
/proc/slabinfo
ext3_inode_cache 21024 23722 1584 2 1 : tunables 24 12
0 : slabdata 11861 11861 0
ext3_inode_cache 41332 41332 1584 2 1 : tunables 24 12
0 : slabdata 20666 20666 0
ray@phoenix:~/work/home/pagecache-management$ echo $(( 1584 * (41332-21024) ))
32167872
Or is there a /proc/sys/vm/* knob that can be tweaked for this
before/after the updatedb?
But yeah, I for one would happily submit patches to upstream authors
to address this there. There's no reason code should be making the
kernel guess its intention on these things.
Ray
next prev parent reply other threads:[~2007-03-03 22:58 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 20:29 Andrew Morton
2007-03-03 20:40 ` Rik van Riel
2007-03-03 21:12 ` Andrew Morton
2007-03-03 21:30 ` Rik van Riel
2007-03-03 21:41 ` bert hubert
2007-03-03 22:14 ` Andrew Morton
2007-03-03 22:19 ` Rik van Riel
2007-03-03 22:26 ` Andrew Morton
2007-03-03 22:28 ` Rik van Riel
2007-03-03 22:38 ` Andrew Morton
2007-03-03 22:56 ` Erik Andersen
2007-03-03 23:01 ` bert hubert
2007-03-03 23:45 ` Andrew Morton
2007-03-06 12:10 ` Pádraig Brady
2007-03-06 21:40 ` Andrew Morton
2007-03-06 21:44 ` Rik van Riel
2007-03-07 11:39 ` Pádraig Brady
2007-03-07 18:50 ` Andrew Morton
2007-03-08 7:59 ` Vaidyanathan Srinivasan
2007-03-08 8:12 ` Andrew Morton
2007-03-03 22:07 ` Andrew Morton
2007-03-03 22:25 ` Rik van Riel
2007-03-03 22:37 ` Andrew Morton
2007-03-03 22:52 ` Andrew Morton
2007-03-04 0:01 ` Rik van Riel
2007-03-04 1:02 ` Andrew Morton
2007-03-04 1:23 ` Rik van Riel
2007-03-04 1:49 ` Andrew Morton
2007-03-04 1:56 ` Rik van Riel
2007-03-04 12:07 ` Andrew Morton
2007-03-04 14:35 ` Peter Zijlstra
2007-03-04 16:01 ` Rik van Riel
2007-03-03 22:58 ` Ray Lee [this message]
2007-03-03 23:34 ` Andrew Morton
2007-03-04 1:02 ` Ray Lee
2007-03-04 1:21 ` Andrew Morton
2007-03-04 0:14 ` Eric St-Laurent
2007-03-04 1:10 ` Andrew Morton
2007-03-04 1:39 ` Rik van Riel
2007-03-04 1:16 ` Lee Revell
2007-03-04 1:39 ` Andrew Morton
2007-03-04 2:35 ` Lee Revell
2007-03-04 4:35 ` Andrew Morton
2007-03-05 11:02 ` Pádraig Brady
2007-03-05 11:12 ` Andrew Morton
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=2c0942db0703031458i540c496fib892240619faa9b2@mail.gmail.com \
--to=madrabbit@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-gmail@madrabbit.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
all inboxes | Powered by JetHome®