From: Nick Piggin <piggin@cyberone.com.au>
To: Nathan Scott <nathans@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
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 18:15:31 +1000 [thread overview]
Message-ID: <416CE423.3000607@cyberone.com.au> (raw)
In-Reply-To: <20041013172352.B4917536@wobbly.melbourne.sgi.com>
Nathan Scott wrote:
>On Wed, Oct 13, 2004 at 12:02:06AM -0700, Andrew Morton wrote:
>
>>Well something else if fishy: how can you possibly achieve only 4MB/sec?
>>
>
>These are 1K writes too remember, so it feels a bit like we
>write 'em out one at a time, sync (though no O_SYNC, or fsync,
>or such involved here). This is on an i686, so 4K pages, and
>using 4K filesystem blocksizes (both xfs and ext2).
>
>
Still shouldn't cause such a big slowdown. Seems like they
might be getting written off the end of the page reclaim
LRU (although in that case it is a bit odd that increasing
the dirty thresholds are improving performance).
I don't think we have any vmscan metrics for this... kswapd
definitely has become more active in 2.6.9-rc. If you're stuck
for ideas, try editing mm/vmscan.c:may_write_to_queue - comment
out the if(current_is_kswapd()) check.
It is a long shot though. Andrew probably has better ideas.
--
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-13 8:15 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 [this message]
2004-10-13 8:39 ` Andrew Morton
2004-10-14 0:53 ` Nathan Scott
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=416CE423.3000607@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@sgi.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