just to let you know the problem described below seems to have been fixed in
2.4.17-rc1. It behaves as it should. Great work!
On Thursday 29 November 2001 21:39, you wrote:
> I am experiencing a bit of strange system behaviour in a vanilla 2.4.16
> kernel (2.95.3, very stable machine etc.)
> I noticed, that after running for a while (day) I had significantly less
> memory available for my simulation program than right after booting.
> Looking at the problem using 'xosview' (or 'free'), I noticed that there
> was a large number of MBs filled with 'buffers' that did not get wiped when
> other programs need the memory. The system seems to rather kill an
> 'offender' than clean out buffers.
> Right after booting, I can allocate about 650MBs memory using the little
> program attached below. After a day (or after running updatedb), under the
> same conditions, even in single user mode with only a shell running (!)
> this is not possible anymore and the program (below), trying to allocate
> only 300-400MBs, gets killed by the system after making it unresponsive for
> many seconds.
> Apparently this problem occurs after running 'updatedb', which fills 'free
> memory' and generates lots of filled cache and buffers on my system.
> This sort of behaviour must have been introduced after 2.4.13, which does
> not show these problems.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:27 EST