On Wed, 5 Dec 2007, Krzysztof Oledzki wrote:
On Wed, 5 Dec 2007, bugme-daemon@xxxxxxxxxxxxxxxxxxx wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=9182
------- Comment #20 from akpm@xxxxxxxx 2007-12-05 13:37 -------
Please monitor the "Dirty:" record in /proc/meminfo. Is it slowly rising
and never falling?
It is slowly rising with respect to a small fluctuation caused by a current load.
Does it then fall if you run /bin/sync?Only a little, by ~1-2MB like in a normal system. But it is not able to fall below a local minimum. So, after a first sync it does not fall more with additional synces.
Compile up usemem.c from
http://www.zip.com.au/~akpm/linux/patches/stuff/ext3-tools.tar.gz and run
usemem -m <N>
where N is the number of megabytes whcih that machine has.
It has 2GB but:
# ./usemem -m 1662 ; echo $?
0
# ./usemem -m 1663 ; echo $?
./usemem: mmap failed: Cannot allocate memory
1
Did this cause /proc/meminfo:Dirty to fall?No.
OK, I booted a kernel without 2:2 memsplit but instead with a standard 3.1:0.9 and even without highmem. So, now I have ~900MB and I am able to set -m to the number of megabytes which themachine has. However, usemem still does does not cause dirty memory usage to fall. :(