From: Andrew Morton <akpm@osdl.org>
To: Marc Singer <elf@buici.com>
Cc: wli@holomorphy.com, elf@buici.com, linux-kernel@vger.kernel.org
Subject: Re: vmscan.c heuristic adjustment for smaller systems
Date: Sat, 17 Apr 2004 22:52:43 -0700 [thread overview]
Message-ID: <20040417225243.0faa6fc4.akpm@osdl.org> (raw)
In-Reply-To: <20040418053857.GC19595@flea>
Marc Singer <elf@buici.com> wrote:
>
> On Sat, Apr 17, 2004 at 08:53:38PM -0700, Andrew Morton wrote:
> > William Lee Irwin III <wli@holomorphy.com> wrote:
> > >
> > > On Sat, Apr 17, 2004 at 04:51:51PM -0700, Andrew Morton wrote:
> > > > I'd assume that setting swappiness to zero simply means that you still have
> > > > all of your libc in pagecache when running ls.
> > > > What happens if you do the big file copy, then run `sync', then do the ls?
> > > > Have you experimented with the NFS mount options? v2? UDP?
> > >
> > > I wonder if the ptep_test_and_clear_young() TLB flushing is related.
> >
> > That, or page_referenced() always returns true on this ARM implementation
> > or some such silliness. Everything here points at the VM being unable to
> > reclaim that clean pagecache.
>
> How can I tell?
Well some more descriptions of what the system does after that copy-to-nfs
would help. Does it _ever_ come good, or is a reboot needed, etc?
What does `vmstat 1' say during the copy, and during the ls?
/proc/vmstats before and after the ls.
Try doing the copy, then when it has finished do the old
memset(malloc(24M)) and monitor the `vmstat 1' output while it runs,
capture /proc/meminfo before and after.
None of the problems you report are present on x86 as far as I can tell,
so...
next prev parent reply other threads:[~2004-04-18 5:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-17 19:38 vmscan.c heuristic adjustment for smaller systems William Lee Irwin III
2004-04-17 21:29 ` Marc Singer
2004-04-17 21:33 ` William Lee Irwin III
2004-04-17 21:52 ` Marc Singer
2004-04-18 1:06 ` William Lee Irwin III
2004-04-18 5:05 ` Marc Singer
2004-04-17 23:21 ` Andrew Morton
2004-04-17 23:30 ` Marc Singer
2004-04-17 23:51 ` Andrew Morton
2004-04-18 0:11 ` Trond Myklebust
2004-04-18 0:23 ` Marc Singer
2004-04-18 3:37 ` Nick Piggin
2004-04-18 4:17 ` William Lee Irwin III
2004-04-18 4:41 ` Nick Piggin
2004-04-18 5:10 ` Marc Singer
2004-04-18 5:19 ` Nick Piggin
2004-04-18 5:35 ` Marc Singer
2004-04-18 5:41 ` Nick Piggin
2004-04-18 23:44 ` Marc Singer
2004-04-18 9:29 ` Russell King
2004-04-18 1:59 ` William Lee Irwin III
2004-04-18 3:53 ` Andrew Morton
2004-04-18 5:38 ` Marc Singer
2004-04-18 5:52 ` Andrew Morton [this message]
2004-04-18 6:15 ` Marc Singer
2004-04-19 0:26 ` Rik van Riel
2004-04-19 0:39 ` Marc Singer
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=20040417225243.0faa6fc4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=elf@buici.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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