From: Andrew Morton <akpm@osdl.org>
To: awesley@acquerra.com.au
Cc: nate.diller@gmail.com, rheflin@atipa.com, linux-kernel@vger.kernel.org
Subject: Re: kernel 2.6.13 buffer strangeness
Date: Fri, 9 Sep 2005 22:41:48 -0700 [thread overview]
Message-ID: <20050909224148.3bf40856.akpm@osdl.org> (raw)
In-Reply-To: <43222DC3.9080609@acquerra.com.au>
Anthony Wesley <awesley@acquerra.com.au> wrote:
>
> How else can it take only 70 seconds to reach 95% dirty when I have 1.3Gb of available RAM and data coming in at 25MBytes/sec and out at 17MBytes/sec? It doesn't make any sense...
What architecture? x86?
If so then bear in mind that your memory is split into 500MB highmem and
800MB lowmem. The kernel might be starting I/O due to the highmem zone
being full of dirty pages. That'd be wrong of it if so - it's supposed to
just fall back to lowmem for the page allocations, but that code has
changed quite a bit in the two years since I got all that working...
You need to run `watch -n1 cat /proc/meminfo' while doing these tests...
next prev parent reply other threads:[~2005-09-10 5:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 9:11 kernel 2.6.13 buffer strangeness Anthony Wesley
2005-09-09 15:09 ` Roger Heflin
2005-09-09 21:39 ` Nate Diller
2005-09-10 0:16 ` Anthony Wesley
2005-09-10 0:35 ` Nate Diller
2005-09-10 1:07 ` Anthony Wesley
2005-09-10 1:47 ` Nate Diller
2005-09-10 2:23 ` Anthony Wesley
[not found] ` <5c49b0ed05090922021b8f8112@mail.gmail.com>
2005-09-10 5:32 ` Anthony Wesley
2005-09-10 6:02 ` kernel 2.6.13 buffer strangeness - FIXED Anthony Wesley
2005-09-10 10:23 ` kernel 2.6.13 buffer strangeness - ext2/3/reiser4/xfs comparison Anthony Wesley
2005-09-10 11:42 ` Andrew Morton
2005-09-10 11:56 ` Anthony Wesley
2005-09-10 0:50 ` kernel 2.6.13 buffer strangeness Anthony Wesley
2005-09-10 5:41 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-09 8:14 Anthony Wesley
2005-09-09 8:24 ` David Lang
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=20050909224148.3bf40856.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=awesley@acquerra.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=nate.diller@gmail.com \
--cc=rheflin@atipa.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