From: Nathan Scott <nathans@sgi.com>
To: Nick Piggin <piggin@cyberone.com.au>, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-xfs@oss.sgi.com
Subject: Re: Page cache write performance issue
Date: Thu, 14 Oct 2004 10:53:00 +1000 [thread overview]
Message-ID: <20041014005300.GA716@frodo> (raw)
In-Reply-To: <20041013013941.49693816.akpm@osdl.org>
On Wed, Oct 13, 2004 at 01:39:41AM -0700, Andrew Morton wrote:
> Nick Piggin <piggin@cyberone.com.au> wrote:
> >
> > Andrew probably has better ideas.
>
> uh, is this an ia32 highmem box?
Yep, it is.
> If so, you've hit the VM sour spot.
> ...
> Basically, *any* other config is fine. 896MB and below, 1.5GB and above.
I just tried switching CONFIG_HIGHMEM off, and so running the
machine with 512MB; then adjusted the test to write 256M into
the page cache, again in 1K sequential chunks. A similar mis-
behaviour happens, though the numbers are slightly better (up
from ~4 to ~6.5MB/sec). Both ext2 and xfs see this. When I
drop the file size down to 128M with this kernel, I see good
results again (as we'd expect).
I'm being pulled onto other issues atm, but in the background
I could try reverting specific changesets if you guys can
suggest anything in particular that might be triggering this?
thanks!
--
Nathan
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-10-14 0:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 5:44 Nathan Scott
2004-10-13 6:19 ` Andrew Morton
2004-10-13 6:39 ` Nathan Scott
2004-10-13 7:02 ` Andrew Morton
2004-10-13 7:23 ` Nathan Scott
2004-10-13 8:15 ` Nick Piggin
2004-10-13 8:39 ` Andrew Morton
2004-10-14 0:53 ` Nathan Scott [this message]
2004-10-14 3:20 ` Andrew Morton
2004-10-14 7:16 ` Nathan Scott
2004-10-14 7:31 ` Nick Piggin
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=20041014005300.GA716@frodo \
--to=nathans@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@oss.sgi.com \
--cc=piggin@cyberone.com.au \
/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