From: Andrew Morton <akpm@osdl.org>
To: Nathan Scott <nathans@sgi.com>
Cc: piggin@cyberone.com.au, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-xfs@oss.sgi.com
Subject: Re: Page cache write performance issue
Date: Wed, 13 Oct 2004 20:20:41 -0700 [thread overview]
Message-ID: <20041013202041.2e7066af.akpm@osdl.org> (raw)
In-Reply-To: <20041014005300.GA716@frodo>
Nathan Scott <nathans@sgi.com> wrote:
>
> 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).
No such problem here, with
dd if=/dev/zero of=x bs=1k count=128k
on a 256MB machine. xfs and ext2.
Can you exhibit this one more than one machine?
Silly question: what does `grep sync' /etc/fstab say over there? ;)
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@osdl.org>
To: Nathan Scott <nathans@sgi.com>
Cc: piggin@cyberone.com.au, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-xfs@oss.sgi.com
Subject: Re: Page cache write performance issue
Date: Wed, 13 Oct 2004 20:20:41 -0700 [thread overview]
Message-ID: <20041013202041.2e7066af.akpm@osdl.org> (raw)
In-Reply-To: <20041014005300.GA716@frodo>
Nathan Scott <nathans@sgi.com> wrote:
>
> 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).
No such problem here, with
dd if=/dev/zero of=x bs=1k count=128k
on a 256MB machine. xfs and ext2.
Can you exhibit this one more than one machine?
Silly question: what does `grep sync' /etc/fstab say over there? ;)
--
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 3:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 5:44 Page cache write performance issue Nathan Scott
2004-10-13 5:44 ` Nathan Scott
2004-10-13 6:19 ` Andrew Morton
2004-10-13 6:19 ` Andrew Morton
2004-10-13 6:39 ` Nathan Scott
2004-10-13 6:39 ` Nathan Scott
2004-10-13 7:02 ` Andrew Morton
2004-10-13 7:02 ` Andrew Morton
2004-10-13 7:23 ` Nathan Scott
2004-10-13 7:23 ` Nathan Scott
2004-10-13 8:15 ` Nick Piggin
2004-10-13 8:15 ` Nick Piggin
2004-10-13 8:39 ` Andrew Morton
2004-10-13 8:39 ` Andrew Morton
2004-10-14 0:53 ` Nathan Scott
2004-10-14 0:53 ` Nathan Scott
2004-10-14 3:20 ` Andrew Morton [this message]
2004-10-14 3:20 ` Andrew Morton
2004-10-14 7:16 ` Nathan Scott
2004-10-14 7:16 ` Nathan Scott
2004-10-14 7:31 ` Nick Piggin
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=20041013202041.2e7066af.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.