lkml.org 
[lkml]   [2004]   [Apr]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: vmscan.c heuristic adjustment for smaller systems
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...

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:02    [W:0.131 / U:0.860 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site