From: Andrew Morton <akpm@osdl.org>
To: Bill Nottingham <notting@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bad caching behavior in 2.6.12rc1
Date: Thu, 24 Mar 2005 15:38:13 -0800 [thread overview]
Message-ID: <20050324153813.5ee0ab1f.akpm@osdl.org> (raw)
In-Reply-To: <20050324232731.GA14812@nostromo.devel.redhat.com>
Bill Nottingham <notting@redhat.com> wrote:
>
> When I upgraded from 2.6.11 to 2.6.12rc1, the VM started
> behaving really badly with respect to caching.
>
> Test box is a 1.5GB laptop.
>
> In typical use, I would open a mailbox A, and then switch
> to mailbox B. Immediately switching back to mailbox A, I
> would find out it was no longer cached. (Using maildirs,
> FWIW.)
>
> Looking at /proc/meminfo, I would see:
>
> LowFree: 8-12MB
> HighFree: 300-400MB
> Cached: 100-200MB
>
> i.e., it was evicting cache when there was plenty of highmem
> available for use.
Where's the rest of the memory gone? A full /proc/meminfo would be useful.
next prev parent reply other threads:[~2005-03-24 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 23:27 Bill Nottingham
2005-03-24 23:38 ` Andrew Morton [this message]
2005-03-25 17:52 ` Bill Nottingham
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=20050324153813.5ee0ab1f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=notting@redhat.com \
/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®