How? From the description I believe it took 16GB in
a zone before we start scanning anon pages when
reclaiming at DEF_PRIORITY?
Would that casue a problem?
We may need better streaming IO detection, anyway.
I have noticed that while heavy sequential reads are fine,
the virtual machines on my desktop system do a lot of whole
block writes. Presumably, a lot of those writes are to the
same blocks, over and over again.
This causes the blocks to be promoted to the active file
list, which ends up growing the active file list to the
point where things from the working set get evicted.
All for file pages that may only get WRITTEN to by the
guests, because the guests cache their own copy whenever
they need to read them!
I'll have to check the page cache code to see if it
keeps frequently written pages as accessed. We may be
better off evicting frequently written pages, and
keeping our cache space for data that is read...
--